Shell not finding binary when attempting to execute it (it's _definitely_ there)
- by eegg
I have a specific set of binaries installed at:
~/.GutenMark/binary/<binaries...>
These were previously working correctly, but for seemingly no reason when I attempt to execute them the shell claims not to find them:
james@anubis:~/.GutenMark/binary$ ls -al
...
-rwxr-xr-x 1 james james 2979036 2009-05-10 13:34 GUItenMark
...
-rwxrwxrwx 1 james james 76952 2009-05-10 13:34 GutenMark
...
-rwxr-xr-x 1 james james 10156 2009-05-10 13:34 GutenSplit
...
james@anubis:~/.GutenMark/binary$ ./GutenMark
bash: ./GutenMark: No such file or directory
james@anubis:~/.GutenMark/binary$
I've tried to isolate the cause of this, with no success. The same happens with zsh, bash, and sh (all giving their appropriate "file not found" error -- this is definitely not a strange output from the binary itself). The same happens either as user james or as root. Nor is it directory specific; if I move the whole directory installation, or just a single binary, to anywhere else, the same happens when attempting to execute it. The same even happens when I put the directory in $PATH and just execute "GutenMark". It also happens when I execute it from a script (I've tried Python's commands module -- though this appears to just call sh).
The problem appears to be specific to the binaries themselves, yet they appear to never actually get executed.
Any ideas?
