I have configured and built "buildroot-2011.05" according to the instructions in http://www.at91.com/linux4sam/bin/view/ ... ldRoot_9x5 .
I am running the root file system on NFS.

If i try to execute any executable file, (.out OR .elf) for example "./test.out", I'm getting the error "-sh: ./test.out: not found".

What could be the cause?

Thanks,

That perhaps the file is not there, or does not have executable attributes.

Try doing "ls -l" in the directory you are trying to run in.

If you have gcc within your file system, try building something like "Hello World" and running ./a.out

Hi there

Check my response on 10 July 2007 UTC to an identical issue ("missing" libraries):
http://www.at91.com/forum/viewtopic.php ... /start,17/

Verify that the runtime libraries (i.e. libc and friends) are accessible in your rootfs.
A static (rather than dynamic) link/build to the libraries is an alternate solution.

One user has also encountered an incompatible kernel (built without ARM EABI) but was compiling userland code for EABI.

The bottom line is that the proper way to read these shell messages is that the rightmost colon is the salient delimiter. The text on the right of that last colon is the error message. The text on the left of that last colon is/are the executable(s) that is/are _reporting_ that error. "xx.out:" means that xx.out (which was started by the shell) needs file(s) but cannot find them. (xx.out is _not_ the file that is missing in this message since there is a colon following it.) The missing file(s) are typically the runtime / dynamic-linking libraries.

Regards