Changeset 37e35d2 for chapter08/introduction.xml
- Timestamp:
- 06/29/2020 07:55:01 AM (4 years ago)
- Branches:
- multilib-10.1
- Children:
- c4804e8
- Parents:
- d4fdde6
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter08/introduction.xml
rd4fdde6 r37e35d2 6 6 ]> 7 7 8 <sect1 id="ch- bootable-introduction">8 <sect1 id="ch-system-introduction"> 9 9 <?dbhtml filename="introduction.html"?> 10 10 11 11 <title>Introduction</title> 12 12 13 <para>It is time to make the LFS system bootable. This chapter 14 discusses creating an <filename>fstab</filename> file, building a 15 kernel for the new LFS system, and installing the GRUB boot loader so 16 that the LFS system can be selected for booting at startup.</para> 13 <para>In this chapter, we start constructing the LFS system in earnest. 14 </para> 15 16 <para>The installation of this software is straightforward. Although in many 17 cases the installation instructions could be made shorter and more generic, 18 we have opted to provide the full instructions for every package to minimize 19 the possibilities for mistakes. The key to learning what makes a Linux system 20 work is to know what each package is used for and why you (or the system) 21 may need it.</para> 22 23 <para>We do not recommend using optimizations. They can make 24 a program run slightly faster, but they may also cause compilation 25 difficulties and problems when running the program. If a package refuses to 26 compile when using optimization, try to compile it without optimization and 27 see if that fixes the problem. Even if the package does compile when using 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 that 30 the <option>-march</option> and <option>-mtune</option> options using values 31 not specified in the book have not been tested. This may cause problems with 32 the toolchain packages (Binutils, GCC and Glibc). The small potential gains 33 achieved in using compiler optimizations are often outweighed by the risks. 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> 37 38 <para>Before the installation instructions, each installation page provides 39 information about the package, including a concise description of what it 40 contains, approximately how long it will take to build, and how much disk 41 space is required during this building process. Following the installation 42 instructions, there is a list of programs and libraries (along with brief 43 descriptions) that the package installs.</para> 44 45 <note><para>The SBU values and required disk space includes test suite data 46 for all applicable packages in <xref linkend="chapter-building-system"/>. SBU 47 values have been calculated using a single CPU core (-j1) for all 48 operations.</para></note> 49 50 <sect2> 51 <title>About libraries</title> 52 53 <para>In general, the LFS editors discourage building and installing static 54 libraries. The original purpose for most static libraries has been made 55 obsolete in a modern Linux system. In addition, linking a static library 56 into a program can be detrimental. If an update to the library is needed 57 to remove a security problem, all programs that use the static library will 58 need to be relinked to the new library. Since the use of static libraries 59 is not always obvious, the relevant programs (and the procedures needed to 60 do the linking) may not even be known.</para> 61 62 <para>In the procedures in this chapter, we remove or disable installation of 63 most static libraries. Usually this is done by passing a 64 <option>--disable-static</option> option to <command>configure</command>. 65 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 general 67 package building process. </para> 68 69 <para>For a more complete discussion of libraries, see the discussion 70 <ulink url="&blfs-root;/view/&short-version;/introduction/libraries.html"> 71 Libraries: Static or shared?</ulink> in the BLFS book.</para> 72 73 </sect2> 17 74 18 75 </sect1>
Note:
See TracChangeset
for help on using the changeset viewer.