Need help to compile Apllication binaries
vapier at gentoo.org
Sat Jan 5 08:05:50 UTC 2008
On Wednesday 07 November 2007, Carmelo AMOROSO wrote:
> harsh poshtiwala wrote:
> > I have flashed uclibc baes kernel and root file system on ARM926
> > EJS based target.
> > I didn't cross compile application binaries with uclibc_small
> > cross compiler, but i had compiled it with arm-linux-gnueabi-
> > glibc_small.
this is probably the source of your problem ... your toolchains are all
f-jucked. build a real toolchain targetting uClibc and it should work fine.
> > When ever we try to execute the any APPLICATION binaries it gives
> > error message file not found
> > #pwd
> > #tcuSw
> > #./shu.out
> > sh: /.shu.out: not found
> > The same happens with all the application binaries.
> I suspect it is failing to load the dynamic linker (yes, the message is
> not self-explaining !)
unfortunately, there's no real way to pass that information up to the user.
the kernel cannot find the interpreter in the ELF header so it returns "file
not found" to the process attempting the exec.
> Check you application with readelf and look for the interpreter entry.
> It has to be
> /lib/ld-uClibc.so.0; then check into your file system if it is there.
readelf does not provide a way to get at that exactly ... looking at the
program headers (-l) will usually provide it in a round-about way. or dump
the .interp section with -x. those lucky people with pax-utils package on
their system can use `scanelf -i` to explicitly get the interpreter :)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 835 bytes
Desc: This is a digitally signed message part.
Url : http://lists.busybox.net/pipermail/uclibc/attachments/20080105/090c23a6/attachment-0002.pgp
More information about the uClibc