On Fri, Dec 14, 2012 at 08:36:08PM -0500, Alexander Spitzer wrote: > Hi Ken, > > Running ldd /tools/bin/bash gives: > linux-vdso.so.1 => (0x00007fff3d955000) > libtinfo.so.5 => /lib/x86_64-linux-gnu/libtinfo.so.5 (0x00007f39676b7000) > libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f39674b3000) > libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f39670f3000) > /lib64/ld-linux-x86-64.so.2 (0x00007f39678ff000) > > which is bad because /tools/lib is nowhere to be found. > I'm not familiar with libtinfo, but I'm currently on my netbook which runs ubuntu and does indeed link bash to it. On my most recent LFS-7.2 desktop I see *from my backups* that /tools/bin/bash was linked to a libncurses.so.5 in /tools. So, your /tools/bin/bash is only using host libraries.
> However, checking a later package such as grep gives: > linux-vdso.so.1 => (0x00007fffe7bff000) > libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f7eb0a62000) > /tools/lib64/ld-linux-x86-64.so.2 => /lib64/ld-linux-x86-64.so.2 > (0x00007f7eb0e42000) That looks odd, libc in /lib instead of /tools, and the loader linked from /tools/lib64 to /lib64. On my backups, everything is in /tools/lib except for the loader which is in /tools/lib64. > > which I'm assuming is good. The result for the other packages is similar to > the one for grep. Is bash the only package with a problem? > Or should the ONLY libraries listed from a ldd check be in /tools/bin (this > would mean that EVERY package is improperly installed) > /tools/lib (apart from the amd64 loader /tools/lib64/ld-linux-x86-64.so.2 which should NOT use /lib64) > > I'm almost positive I only took a break after finishing chapter 5. Thought > it seems that bash is the problem, is it possible that I didn't resume the > environment properly for chapter 6? > > Thanks for the help. At the moment, I don't recognize your results. Usually, people who get the correct results from the sanity checks get a good build. Perhaps there is something different about _how_ you built this. What host distro are you using ? Did you check all the host system requirements ? But, in the absence of any other information (your loader in /tools/lib64 apparently using a loader in /lib64 really perplexes me!), I don't think I know what is wrong. Maybe someone else will recognize the symptoms. Did you run the sanity check after gcc in chapter 5 ? ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
