Changeset 8d5322e for chapter08/introduction.xml
- Timestamp:
- 11/18/2022 07:41:41 AM (18 months ago)
- Branches:
- multilib
- Children:
- 46405a5b
- Parents:
- 16a1647 (diff), 7115c88 (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. - File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter08/introduction.xml
r16a1647 r8d5322e 21 21 may need it.</para> 22 22 23 <para>We do not recommend using optimizations. They can make23 <para>We do not recommend using customized optimizations. They can make 24 24 a program run slightly faster, but they may also cause compilation 25 difficulties and problems when running the program. If a package refuses to26 compile w hen using optimization, try to compile it without optimization and27 see if that fixes the problem. Even if the package does compile when using25 difficulties, and problems when running the program. If a package refuses to 26 compile with a customized optimization, try to compile it without 27 optimization and see if that fixes the problem. Even if the package does compile when using a customized 28 28 optimization, there is the risk it may have been compiled incorrectly because 29 of the complex interactions between the code and build tools. Also note that29 of the complex interactions between the code and the build tools. Also note that 30 30 the <option>-march</option> and <option>-mtune</option> options using values 31 31 not specified in the book have not been tested. This may cause problems with 32 32 the toolchain packages (Binutils, GCC and Glibc). The small potential gains 33 achieved in using compiler optimizations are often outweighed by the risks.33 achieved by customizing compiler optimizations are often outweighed by the risks. 34 34 First-time builders of LFS are encouraged to build without custom 35 optimizations. The subsequent system will still run very fast and be stable 36 at the same time.</para> 35 optimizations.</para> 36 37 <para>On the other hand, we keep the optimizations enabled by the default 38 configuration of the packages. In addition, we sometimes explicitly enable an 39 optimized configuration provided by a package but not enabled by 40 default. The package maintainers have already tested these configurations 41 and consider them safe, so it's not likely they would break the build. 42 Generally the default configuration already enables <option>-O2</option> 43 or <option>-O3</option>, so the resulting system will still run very fast 44 without any customized optimization, and be stable at the same time.</para> 37 45 38 46 <para>Before the installation instructions, each installation page provides … … 43 51 descriptions) that the package installs.</para> 44 52 45 <note><para>The SBU values and required disk space include stest suite data53 <note><para>The SBU values and required disk space include test suite data 46 54 for all applicable packages in <xref linkend="chapter-building-system"/>. SBU 47 55 values have been calculated using a single CPU core (-j1) for all … … 49 57 50 58 <sect2> 51 <title>About libraries</title>59 <title>About Libraries</title> 52 60 53 61 <para>In general, the LFS editors discourage building and installing static 54 libraries. The original purpose for most static libraries hasbeen made62 libraries. Most static libraries have been made 55 63 obsolete in a modern Linux system. In addition, linking a static library 56 64 into a program can be detrimental. If an update to the library is needed 57 to remove a security problem, all programs that usethe static library will58 need to be relinked tothe new library. Since the use of static libraries65 to remove a security problem, every program that uses the static library will 66 need to be relinked with the new library. Since the use of static libraries 59 67 is not always obvious, the relevant programs (and the procedures needed to 60 68 do the linking) may not even be known.</para> 61 69 62 <para> In the procedures in this chapter, weremove or disable installation of70 <para>The procedures in this chapter remove or disable installation of 63 71 most static libraries. Usually this is done by passing a 64 72 <option>--disable-static</option> option to <command>configure</command>. 65 73 In other cases, alternate means are needed. In a few cases, especially 66 glibc and gcc, the use of static libraries remains essential to the general74 Glibc and GCC, the use of static libraries remains an essential feature of the 67 75 package building process. </para> 68 76 69 <para>For a more complete discussion of libraries, see the discussion77 <para>For a more complete discussion of libraries, see 70 78 <ulink url="&blfs-book;introduction/libraries.html"> 71 79 Libraries: Static or shared?</ulink> in the BLFS book.</para>
Note:
See TracChangeset
for help on using the changeset viewer.