Raspberry Pi cpuminer error: -bash: ./minerd: No such file or directory I created a cpuminer instance for my Raspberry Pi derived from this tutorial.  Apparently, I've correctly configured the implementation because I can run the example provided in the README:

./cpuminer -u alexanderjsingleton.Pericles -p pass -o stratum+tcp://stratum.slushpool.com:3333 -t cputhreads




Apparently, that command is indeed the example because I'm not seeing any feedback displayed within my slushpool-account dashboard for that worker. 
 However, according to this StackExchange:Bitcoin post, the appropriate cpuminer-syntax should be:

./minerd -u alexanderjsingleton.Pericles -p pass -o stratum+tcp://stratum.slushpool.com:3333 -t cputhreads


but that command returns the following error:

   ./minerd -h --algo scrypt --scantime 33  --url stratum+tcp://stratum.slushpool.com:3333 --userpass [alexanderjsingleton.Pericles]:[password] --threads 1 --retries -1 -P
-bash: ./minerd: No such file or directory


In any case, this is my first experiment with actual Bitcoin-mining, so I'd appreciate any guidance whatsoever to start mining on my first block- thank you!
The original CPUMiner software made an executable named minerd. You are using a fork of the CPUMiner software which changed the executable produced to be named cpuminer. The minerd ... command will not work because that executable file does not exist as it is not created. If you are looking up any instructions for using CPUMiner and it says to do ./minerd ..., just do ./cpuminer ... instead. Note that because you are not using the original CPUMiner software not all example commands and options will be the same or result in the same behavior.

There are multiple reasons that you do not see anything on your Slush dashboard. First of all, you are connected to a Bitcoin mining pool and yet you are using the Scrypt PoW algorithm. Bitcoin does not use Scrypt, so whatever you are mining is invalid. Secondly, your hashrate is so low that you are not finding any shares (besides the fact that they will be invalid as you are using the wrong algo), so Slushpool does not know anything about this your worker as it has not received anything back from it.