From 73b2841ee14caae80ea8a2bbaa1cb7e2c21e666f Mon Sep 17 00:00:00 2001 From: Bruce Dubbs Date: Sun, 15 Mar 2015 23:29:31 +0000 Subject: Remove non-essential static libraries from the installation. Added a new section in Chapter 6 Introduction, supressed many static libraries in different packages, and removed the remaining in the Cleaning Up section. git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@10880 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689 --- chapter06/introduction.xml | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) (limited to 'chapter06/introduction.xml') diff --git a/chapter06/introduction.xml b/chapter06/introduction.xml index a3a8b8829..ae0e54c58 100644 --- a/chapter06/introduction.xml +++ b/chapter06/introduction.xml @@ -55,4 +55,29 @@ The SBU values and required disk space includes test suite data for all applicable packages in Chapter 6. + + About libraries + + In general, the LFS editors discourage building and installing static + libraries. The original purpose for most static libraries has been made + obsolete in a modern Linux system. In addition linking a static library + into a program can be detrimental. If an update to the library is needed + to remove a security problem, all programs that use the static library will + need to be relinked to the new library. Since the use of static libraries + is not always obvious, deciding which programs (and the procedures needed to + do the linking) may not even be known. + + In the prcedures in Chapter 6, we remove or disable installation of + most static libraries. In a few cases, especially glibc and gcc, the use + of static libraries remains essential to the general package building + process. Usually this is done by passing a + option to configure. + In other cases, alternate means are needed. + + For a more complete discussion of libraries, see the discussion + + Libraries: Static or shared? in the BLFS book. + + + -- cgit v1.2.3-54-g00ecf