Changeset b59b371 for chapter08/introduction.xml

Timestamp:

11/19/2022 08:27:13 AM (18 months ago)

Author:

Xi Ruoyao <xry111@…>

Branches:

xry111/clfs-ng

Children:

2ef64c4

Parents:

4d3f41c (diff), 651f491 (diff)
Note: this is a merge changeset, the changes displayed below correspond to the merge itself.
Use the (diff) links above to see all the changes relative to each parent.

Message:

Merge remote-tracking branch 'origin/trunk' into xry111/clfs-ng

File:

• chapter08/introduction.xml (modified) (3 diffs)

chapter08/introduction.xml

@@ -21 +21 @@
   may need it.</para>
 
-  <para>We do not recommend using optimizations.  They can make
+  <para>We do not recommend using customized optimizations.  They can make
   a program run slightly faster, but they may also cause compilation
-  difficulties and problems when running the program.  If a package refuses to
-  compile when using optimization, try to compile it without optimization and
-  see if that fixes the problem. Even if the package does compile when using
+  difficulties, and problems when running the program.  If a package refuses to
+  compile with a customized optimization, try to compile it without
+  optimization and see if that fixes the problem. Even if the package does compile when using a customized
   optimization, there is the risk it may have been compiled incorrectly because
-  of the complex interactions between the code and build tools.  Also note that
+  of the complex interactions between the code and the build tools.  Also note that
   the <option>-march</option> and <option>-mtune</option> options using values
   not specified in the book have not been tested. This may cause problems with
   the toolchain packages (Binutils, GCC and Glibc).  The small potential gains
-  achieved in using compiler optimizations are often outweighed by the risks.
+  achieved by customizing compiler optimizations are often outweighed by the risks.
   First-time builders of LFS are encouraged to build without custom
-  optimizations. The subsequent system will still run very fast and be stable
-  at the same time.</para>
+  optimizations.</para>
+
+  <para>On the other hand, we keep the optimizations enabled by the default
+  configuration of the packages.  In addition, we sometimes explicitly enable an
+  optimized configuration provided by a package but not enabled by
+  default.  The package maintainers have already tested these configurations
+  and consider them safe, so it's not likely they would break the build.
+  Generally the default configuration already enables <option>-O2</option>
+  or <option>-O3</option>, so the resulting system will still run very fast
+  without any customized optimization, and be stable at the same time.</para>
 
   <para>Before the installation instructions, each installation page provides
@@ -43 +51 @@
   descriptions) that the package installs.</para>
 
-  <note><para>The SBU values and required disk space includes test suite data
+  <note><para>The SBU values and required disk space include test suite data
   for all applicable packages in <xref linkend="chapter-building-system"/>. SBU
   values have been calculated using a single CPU core (-j1) for all
@@ -49 +57 @@
 
   <sect2>
-    <title>About libraries</title>
+    <title>About Libraries</title>
 
     <para>In general, the LFS editors discourage building and installing static
-    libraries.  The original purpose for most static libraries has been made
+    libraries.  Most static libraries have 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
+    to remove a security problem, every program that uses the static library will
+    need to be relinked with the new library.  Since the use of static libraries
     is not always obvious, the relevant programs (and the procedures needed to
     do the linking) may not even be known.</para>
 
-    <para>In the procedures in this chapter, we remove or disable installation of
+    <para>The procedures in this chapter remove or disable installation of
     most static libraries. Usually this is done by passing a
     <option>--disable-static</option> option to <command>configure</command>.
     In other cases, alternate means are needed. In a few cases, especially
-    glibc and gcc, the use of static libraries remains essential to the general
+    Glibc and GCC, the use of static libraries remains an essential feature of the
     package building process. </para>
 
-    <para>For a more complete discussion of libraries, see the discussion
+    <para>For a more complete discussion of libraries, see
     <ulink url="&blfs-book;introduction/libraries.html">
     Libraries: Static or shared?</ulink> in the BLFS book.</para>