Tim Tassonis wrote:
Hi all
I noticed that during LFS build, some programs will not work after they
are installed, because their libraries are in /tools/lib and /tools/lib is
not in the search path of the dynamic linker.
An example is e2fsprogs, ldd on /bin/chattr results in:
linux-vdso.so.1 (0x00007ffd8a1e8000)
libe2p.so.2 => /lib/libe2p.so.2 (0x00007f827f8e0000)
libcom_err.so.2 => /lib/libcom_err.so.2 (0x00007f827f6dc000)
libblkid.so.1 => not found
libc.so.6 => /lib/libc.so.6 (0x00007f827f322000)
libpthread.so.0 => /lib/libpthread.so.0 (0x00007f827f104000)
/lib64/ld-linux-x86-64.so.2 (0x00007f827faea000)
So, I thought it would be an idea to create a tools.conf in
/etc/ld.so.conf.d after installation of glibc and run /sbin/ldconfig, so
programs find the missing libraries. As I assume that those entries come
last, the programs will link to the proper libraries as soon as they
become available. Or is there anything problematic with this solution?
Why? In Chapter 6 you don't need anything that would require that. The
partial chroot environment is not meant to be completely functional until
the end of Chapter 6 at which point you can remove /mnt/lfs/tools and the
/tools symlink that points to it.
-- Bruce
--
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
