the below is from personal experience and does not rely on updating ld.so.cache... i am sure there is a more *correct* way to deal with this. (i am upgrading to the 2.95.3 toolchain and i assumed i could just use ld and libc in my RFS - but i ran into the same issue as you Rafael)
run the following command on your host. objdump -s --section=.interp libc-2.2.2.so this gives you the assumed path to ld. i have been unable to get a working system unless ld.so and libc are at this location my understanding is: you set the proposed locations for libc and ld when you run configure for libc ( - i have libc and ld in /lib on my RFS ) i worked around the below mentioned problem by setting --libdir=/lib you can also use --prefix and --exec-prefix NOTE: watch out with make install as the cross binaries can end up overwriting the hosts. you can set install_root as a make variable but i have had some mixed results doing this. hope this helps :]k -----Original Message----- From: Rafael Rodr�guez Velilla [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 19, 2001 6:08 AM To: linux-arm Subject: Re: GLIBC_2.2 not found > Okay, I suspected that and actually had tried it, I get that > other error message (so, that's adding /lib/ld-2.2.2.so and > ldconfig again): > > [snip snip] > VFS: Mounted root (ext2 filesystem). > Freeing init memory: 44K > init: errKernel panic: Attempted to kill init! > or while loading shared libraries: libc.so.6: cannot load shared object file: No > such file or directory > > However: > [yves@Pilmuir ram]$ ls -l lib/libc* > -rwxr-xr-x 1 root root 1153972 Dec 18 15:39 lib/libc-2.2.2.so > lrwxrwxrwx 1 root root 13 Dec 18 15:40 lib/libc.so.6 -> libc-2.2.2.so > > so the library _is_ there... I had the same message and the problem was that the loader searched in the same path as I compiled it in my developing environment, so I had to create in the target a symbolic link in the root directory named /arm-tools/arm-linux pointing into the root directory (my libraries where compiled under /arm-tools/arm-linux/lib. I don't know why it is that way, but I couldn't solve it in any other way. Maybe you are having a similar problem. -- Rafael Rodr�guez Velilla [EMAIL PROTECTED] Telef�nica I+D http://www.tid.es Telf: +34 - 91 337 4270 _______________________________________________ http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm Please visit the above address for information on this list. _______________________________________________ http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm Please visit the above address for information on this list.
