sdjf wrote:As others have said, the file name appears to be cancount*.
Everyone who has said that clearly did not read the original post carefully enough. Specifically, the output from "file" shows that the binary is indeed called "cancount". The reference to "cancount*" is in the output of an "ls -lisF".
sdjf wrote:If it requires input or arguments, then the "not found" message you are getting may be telling you that "cancount*" is not finding any arguments or input.
It is highly unlikely that the binary itself is printing the message "-sh: ./cancount: No such file or directory". That error, when the file does in fact exist, basically can only mean that the dynamic loader required by the binary is not present.
Since at least some binaries work, there must be a
dynamic loader present. So the suspect binary is evidently compiled to use a different loader path than the rest of the system. Compiling the program locally should fix that, as might the command:
Code: Select all
ln -s ld-linux.so.3 /lib/ld-linux-armhf.so.3
Not having an "ldd" command is certainly unusual, and it may or may not be part of a bigger problem. But it is really not required to diagnose or fix the original issue.