Command not found problem in Linux-Ubuntu terminal

Question

My friend is having problem in trying to call make to compile an application which both me and a second friend have previously successfully compiled.

The file uses a "linux-devkit" pack that possess a /bin subdirectory containing lots of file called arm-arago-linux-gnueabi-something that are essentially executable files (e.g. one is arm-arago-linux-gnueabi-gcc which is essentially the GCC compiler).

Part of the compile process when we call make install in the Makefile directories of our project consists in calls to such "linux-devkit files". When I or my second friend call the command in the Linux terminal, everything runs fine to the end. But when my friends do it, an error message appears:

arm-arago-linux-gnueabi-gcc: No such command found

(Note: translated from a Portuguese Ubuntu)

After doing countless tests we did managed to find an interesting difference: if we go by Terminal to the ~/linux-devkit/bin folder and call arm-arago-linux-gnueabi-gcc in one of the two working systems, the answer is one that essentially tells the file was found, but command specifications are lacking:

arm-arago-linux-gnueabi-gcc: no input files

and this was a expected error message. But when my friend with the problem executes the same command, the error message is:

bash: ./arm-arago-linux-gnueabi-gcc: File or directory not found

(Note: translated from a Portuguese Ubuntu)

It is as if the Terminal simply wasn't finding the file to use it, even tough it appears when ls is called as well as when using Nautilus!

Or user-permissions for those files are 100% equal, so it can't be a problem there. Does anybody have any guess on what's going on?

---

EDIT:

Here is the answer I got, Volker Siegel:

I'm sure file is in place...

Thats is output, thanks for help.

~/re8k/linux-devkit/bin$ export LC_ALL=C
~/re8k/linux-devkit/bin$ command -v arm-arago-linux-gnueabi-gcc
~/re8k/linux-devkit/bin$ ls -ld ~/re8k/linux-devkit ~/re8k/linux-devkit/bin ./arm-arago-linux-gnueabi-gcc
-rwxr-xr-x  1 diogenes diogenes 448843 Jul  1  2011 ./arm-arago-linux-gnueabi-gcc
drwxr-xr-x 12 diogenes diogenes   4096 Apr 15 17:28 /home/diogenes/re8k/linux-devkit
drwxr-xr-x  2 diogenes diogenes   4096 Sep  3 10:59 /home/diogenes/re8k/linux-devkit/bin
~/re8k/linux-devkit/bin$ head -1 ./arm-arago-linux-gnueabi-gcc
ELF��4�g4('$44�4�44�4������������HH�H�DDQ�tdR�td���/l!��ԟX-linux.so.2GNUGNUI������,�_�_b�
diogenes@diogenes-VirtualBox:~/re8k/linux-devkit/bin$ mount | grep "\s$(stat -c%m .)\s"
/dev/sda1 on / type ext4 (rw,errors=remount-ro)

EDIT 2:

diogenes@diogenes-VirtualBox:~/re8k/linux-devkit/bin$ ./arm-arago-linux-gnueabi-gcc
bash: ./arm-arago-linux-gnueabi-gcc: No such file or directory

A Print Screen to complement:

Solution

When Volker Siegel suggested problems with libraries, a correspondent that also works with Linux told us that he had the same problem and the cause was precisely that some libraries were missing.

We run the sudo apt-get install ia32-libs on Terminal as suggested by Volker, but the system reported that this lib wasn't available anymore, suggesting we should maybe install this other libs:

lib32z1 
lib32ncurses5 
lib32bz2-1.0

After installing them, the problem was solved.

Comments

[Momergil]

#PetrNovak yes, I'm sure (??!!) - remembering that it appears both with Nautilus as well as with ls in Terminal

[Momergil]

I edited my question with the answer I got from my friend who tested you suggestion.

[Volker Siegel]

Strange... looks all normal for now. I forgot, can you run the command itself too with the english messages, and add them? Take care to copy/paste the messages without change (so we can google for the exact text)

[Momergil]

ok, I added a EDIT 2 section with the reply

[Volker Siegel]

Are you running a 64bit box? Do you know you have the 32bit versions of the libraries installed? Just try sudo apt-get install ia32-libs, it will tell you if it's already installed.

[Volker Siegel]

Ok, great! I'm pretty sure by now that missing ia32-libs was the problem because I have found similar cases. That "No such file or directory" is one of the most missleading error messages on Linux/Unix systems. It is the kernel trying to use the 32bit linker for a 32bit binary, but that's missing.