Changeset 9506f85 for chapter06/introduction.xml
- Timestamp:
- 02/05/2006 11:42:02 AM (19 years ago)
- Children:
- 9442d266
- Parents:
- 3a0a57c
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter06/introduction.xml
r3a0a57c r9506f85 1 1 <?xml version="1.0" encoding="ISO-8859-1"?> 2 <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [ 2 <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" 3 "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [ 3 4 <!ENTITY % general-entities SYSTEM "../general.ent"> 4 5 %general-entities; 5 6 ]> 7 6 8 <sect1 id="ch-system-introduction"> 7 <title>Introduction</title> 8 <?dbhtml filename="introduction.html"?> 9 <?dbhtml filename="introduction.html"?> 9 10 10 <para>In this chapter, we enter the building site and start 11 constructing the LFS system in earnest. That is, we chroot into the 12 temporary mini Linux system, make a few final preparations, and then 13 begin installing the packages.</para> 11 <title>Introduction</title> 14 12 15 <para>The installation of this software is straightforward. Although 16 in many cases the installation instructions could be made shorter and 17 more generic, we have opted to provide the full instructions for every 18 package to minimize the possibilities for mistakes. The key to 19 learning what makes a Linux system work is to know what each package 20 is used for and why the user (or the system) needs it. For every 21 installed package, a summary of its contents is given, followed by 22 concise descriptions of each program and library the package 23 installed.</para> 13 <para>In this chapter, we enter the building site and start constructing the 14 LFS system in earnest. That is, we chroot into the temporary mini Linux system, 15 make a few final preparations, and then begin installing the packages.</para> 24 16 25 <para>If using the compiler optimizations provided in this chapter, 26 please review the optimization hint at <ulink 27 url="&hints-root;optimization.txt"/>. Compiler optimizations can make 28 a program run slightly faster, but they may also cause compilation 29 difficulties and problems when running the program. If a package 30 refuses to compile when using optimization, try to compile it without 31 optimization and see if that fixes the problem. Even if the package 32 does compile when using optimization, there is the risk it may have 33 been compiled incorrectly because of the complex interactions between 34 the code and build tools. Also note that the <option>-march</option> 35 and <option>-mtune</option> options may cause problems with the 36 toolchain packages (Binutils, GCC and Glibc). The small potential 37 gains achieved in using compiler optimizations are often outweighed by 38 the risks. First-time builders of LFS are encouraged to build without 39 custom optimizations. The subsequent system will still run very fast 40 and be stable at the same time.</para> 17 <para>The installation of this software is straightforward. Although in many 18 cases the installation instructions could be made shorter and more generic, 19 we have opted to provide the full instructions for every package to minimize 20 the possibilities for mistakes. The key to learning what makes a Linux system 21 work is to know what each package is used for and why the user (or the system) 22 needs it. For every installed package, a summary of its contents is given, 23 followed by concise descriptions of each program and library the package 24 installed.</para> 41 25 42 <para>The order that packages are installed in this chapter needs to 43 be strictly followed to ensure that no program accidentally acquires a 44 path referring to <filename class="directory">/tools</filename> 45 hard-wired into it. For the same reason, do not compile packages in 46 parallel. Compiling in parallel may save time (especially on dual-CPU 47 machines), but it could result in a program containing a hard-wired 48 path to <filename class="directory">/tools</filename>, which will 49 cause the program to stop working when that directory is 50 removed.</para> 26 <para>If using the compiler optimizations provided in this chapter, please 27 review the optimization hint at <ulink url="&hints-root;optimization.txt"/>. 28 Compiler optimizations can make a program run slightly faster, but they may 29 also cause compilation difficulties and problems when running the program. 30 If a package refuses to compile when using optimization, try to compile it 31 without optimization and see if that fixes the problem. Even if the package 32 does compile when using optimization, there is the risk it may have been 33 compiled incorrectly because of the complex interactions between the code 34 and build tools. Also note that the <option>-march</option> and 35 <option>-mtune</option> options may cause problems with the toolchain packages 36 (Binutils, GCC and Glibc). The small potential gains achieved in using 37 compiler optimizations are often outweighed by the risks. First-time builders 38 of LFS are encouraged to build without custom optimizations. The subsequent 39 system will still run very fast and be stable at the same time.</para> 51 40 52 <para>Before the installation instructions, each installation page53 provides information about the package, including a concise 54 description of what it contains, approximately how long it will take 55 to build, how much disk space is required during this building 56 process, and any other packages needed to successfully build the 57 package. Following the installation instructions, there is a list of 58 programs and libraries (along with brief descriptions of these) that 59 the package installs.</para>41 <para>The order that packages are installed in this chapter needs to be 42 strictly followed to ensure that no program accidentally acquires a path 43 referring to <filename class="directory">/tools</filename> hard-wired into 44 it. For the same reason, do not compile packages in parallel. Compiling in 45 parallel may save time (especially on dual-CPU machines), but it could result 46 in a program containing a hard-wired path to <filename 47 class="directory">/tools</filename>, which will cause the program to stop 48 working when that directory is removed.</para> 60 49 61 <note><para>At this point, you may wish to keep your finished temporary 62 tools for use in future LFS builds by creating a tarball of the 63 <filename class="directory">/tools</filename> directory and 64 storing it in a safe location.</para></note> 50 <para>Before the installation instructions, each installation page provides 51 information about the package, including a concise description of what it 52 contains, approximately how long it will take to build, how much disk space 53 is required during this building process, and any other packages needed to 54 successfully build the package. Following the installation instructions, 55 there is a list of programs and libraries (along with brief descriptions of 56 these) that the package installs.</para> 57 58 <note> 59 <para>At this point, you may wish to keep your finished temporary 60 tools for use in future LFS builds by creating a tarball of the 61 <filename class="directory">/tools</filename> directory and 62 storing it in a safe location.</para> 63 </note> 65 64 66 65 </sect1> 67
Note:
See TracChangeset
for help on using the changeset viewer.