On Fri, 2011-04-22 at 09:36 +0200, Giuseppe Sacco wrote: > Hi, > I made a few tests on this report and I found that the loader is not > looking at the right directories. Please have a look at this: [...] > Please note that on both system (outside of chroot) /lib64 is a link > to /lib. I think that's normal; however /lib should be higher up the library search path than /lib64. What does 'ldd /bin/sh' say in the running system? [...] > Beside the very last problem (I will intestigate about it), how do > initramfs-tools create the lib and lib64 trees? Does it use a > configuration file? It uses ldd to find which libraries each executable is linked to, and copies them to the same locations they were found in the running system. (Exception: where the library is optimised for specific CPU features, it substitutes the unoptimised alternate from the parent directory.) However, it does not copy the ld.so configuration files, and it does not unset LD_LIBRARY_PATH. Also, it does not use 'readlink -f' to resolve symbolic links, which I think would solve this particular issue. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse.
Attachment:
signature.asc
Description: This is a digitally signed message part