> 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.
