On Fri, Mar 18, 2016 at 09:35:59PM -0400, Glenn Becker wrote: > > For the problem itself, check the final commands in section 6.18 > > (bzip2) - we copy the progs to /bin and the lib to /lib, and make > > symlinks. I guess that the library symlink is broken. > > > > > Does this reveal anything out of the ordinary: > > root:/sources# ls -la ../../lib/libbz2.so.1.0 > lrwxrwxrwx 1 root root 15 Mar 18 09:50 ../../lib/libbz2.so.1.0 -> > libbz2.so.1.0.6 > > Glenn
Dunno, I don't understand it. Maybe it is me, but I think you are listing something two directories above /sources, in chroot. In chroot, /sources is a top-level directory, so /sources/../ is the same as / and I do not have any idea what ../../ is - but at a guess, just a redundant ../ in *this* context. Try ls -l /lib/libbz2.so* and ls -l /usr/lib/libbz2.so* Symlinks often catch people out in trying to understand where they are pointing : everything is relevant to the link, so for example ln -s bar /usr/bin/foo will symlink /usr/bin/foo to bar in the same directory, i.e. /usr/bin/bar (and file will then report a broken symlink if bar does not exist there). Symilarly, ln -s ../../lib/libfoo.so.9 /usr/lib/libfoo.so would link /usr/lib/libfoo.so to (broken dwon into stages) ../ /usr ../../ /lib ../../libfoo.so.9 /libfoo.so.9 Also, if you have built 'file' in chroot (I don't have the book open at the moment, so not sure) run file on those arguments. I suspect that one or more of the symlinks is broken. If it is, also check the symlinks for the programs. ĸen -- This email was written using 100% recycled letters. -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
