zlib instructions - 'rm /lib/libz.so'?

Randy McMurchy lfs.user at mcmurchy.com
Mon Sep 14 15:19:37 MDT 2009


Bruce Dubbs wrote:
> Bryan Kadzban wrote:
> 
>> But we don't put *any* .so (or .a) files into /lib, because the only
>> reason for /lib is to hold libraries that are required before /usr may
>> be mounted (i.e. early bootscripts).  And when you're compiling -- which
>> is the only time .so or .a files are used -- /usr had better be mounted.
>> :-)
> 
> Actually .so files are used any time a dynamically linked executable needs them, 
> not just when 'compiling'.  But I think you know that.

Yeah, but dynamically linked executables never need them (unless of course
the package only provides a .so or .a file. Typically, what is needed for
dynamically linked packages are files such as libfile.so.1. That is why we
leave libfile.so.1 and libfile.so.1.37 in /lib.

So, actually, .so and .a files are really only needed at compile time for
other packages. :-)


> Actually, I think we may have several unnecessary files in /lib.  I'm not sure 
> why libhistory

Probably for the bash shell.


> , libnss*,

These are Glibc files used for resolving names, likely needed in single user mode.


> libpcre,

Probably bash again.


More information about the lfs-dev mailing list