On 02/12/2018 08:04 PM, Bruce Dubbs wrote:
Tim Tassonis wrote:
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:
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)
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
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.
Well, it was just an idea, so one can test freshly installed stuff right
away. I got unsure if I made a mistake during chapter 6 when I executed
"clear" in my shell and it gave me an error about missing libncurses.
After some thinking and checking, I realized that this due to libncurses
still in /tools.
I can well live with the current situation, I just thought it would be a
bit nicer if everything worked right away. Just a thought.
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?
Q: What is the most annoying thing in e-mail?