Changeset 3b45abb for chapter05/introduction.xml
- Timestamp:
- 01/22/2006 12:21:07 PM (19 years ago)
- Children:
- b4cd3c5
- Parents:
- d1ae0cb
- File:
-
- 1 edited
-
chapter05/introduction.xml (modified) (1 diff)
Legend:
- Unmodified
- Added
- Removed
-
chapter05/introduction.xml
rd1ae0cb r3b45abb 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-tools-introduction"> 7 <title>Introduction</title> 8 <?dbhtml filename="introduction.html"?> 9 <?dbhtml filename="introduction.html"?> 9 10 10 <para>This chapter shows how to compile and install a minimal Linux 11 system. This system will contain just enough tools to start 12 constructing the final LFS system in <xref 13 linkend="chapter-building-system"/> and allow a working environment 14 with more user convenience than a minimum environment would.</para> 11 <title>Introduction</title> 15 12 16 <para>There are two steps in building this minimal system. The first 17 step is to build a new and host-independent toolchain (compiler, 18 assembler, linker, libraries, and a few useful utilities). The second 19 step uses this toolchain to build the other essential tools.</para>13 <para>This chapter shows how to compile and install a minimal Linux system. 14 This system will contain just enough tools to start constructing the final 15 LFS system in <xref linkend="chapter-building-system"/> and allow a working 16 environment with more user convenience than a minimum environment would.</para> 20 17 21 <para>The files compiled in this chapter will be installed under the 22 <filename class="directory">$LFS/tools</filename> directory to keep 23 them separate from the files installed in the next chapter and the 24 host production directories. Since the packages compiled here are 25 temporary, we do not want them to pollute the soon-to-be LFS 26 system.</para> 18 <para>There are two steps in building this minimal system. The first step 19 is to build a new and host-independent toolchain (compiler, assembler, 20 linker, libraries, and a few useful utilities). The second step uses this 21 toolchain to build the other essential tools.</para> 27 22 28 <important><para>Before issuing the build instructions for a package, the package 29 should be unpacked as user <emphasis>lfs</emphasis>, and a 30 <command>cd</command> into the created directory should be performed. The build 31 instructions assume that the <command>bash</command> shell is in use.</para></important> 23 <para>The files compiled in this chapter will be installed under the 24 <filename class="directory">$LFS/tools</filename> directory to keep them 25 separate from the files installed in the next chapter and the host 26 production directories. Since the packages compiled here are temporary, 27 we do not want them to pollute the soon-to-be LFS system.</para> 32 28 33 <para>Several of the packages are patched before compilation, but only 34 when the patch is needed to circumvent a problem. A patch is often 35 needed in both this and the next chapter, but sometimes in only one or 36 the other. Therefore, do not be concerned if instructions for a downloaded 37 patch seem to be missing. Warning messages about 38 <emphasis>offset</emphasis> or <emphasis>fuzz</emphasis> may 39 also be encountered when applying a patch. Do not worry about these 40 warnings, as the patch was still successfully applied.</para> 29 <important> 30 <para>Before issuing the build instructions for a package, the package 31 should be unpacked as user <systemitem class="username">lfs</systemitem>, 32 and a <command>cd</command> into the created directory should be performed. 33 The build instructions assume that the <command>bash</command> shell is 34 in use.</para> 35 </important> 41 36 42 <para>During the compilation of most packages, there will be several 43 warnings that scroll by on the screen. These are normal and can safely 44 be ignored. These warnings are as they appear—warnings about 45 deprecated, but not invalid, use of the C or C++ syntax. C standards 46 change fairly often, and some packages still use the older standard. 47 This is not a problem, but does prompt the warning.</para> 37 <para>Several of the packages are patched before compilation, but only when 38 the patch is needed to circumvent a problem. A patch is often needed in both 39 this and the next chapter, but sometimes in only one or the other. Therefore, 40 do not be concerned if instructions for a downloaded patch seem to be missing. 41 Warning messages about <emphasis>offset</emphasis> or <emphasis>fuzz</emphasis> 42 may also be encountered when applying a patch. Do not worry about these 43 warnings, as the patch was still successfully applied.</para> 48 44 49 <important><para>After installing each package, delete its source and build 50 directories, unless specifically instructed otherwise. Deleting the 51 sources prevents mis-configuration when the same package is reinstalled later. 52 Only three of the packages need to retain the source and build directories in 53 order for their contents to be used by later commands. Pay special attention to 54 these reminders.</para></important>45 <para>During the compilation of most packages, there will be several warnings 46 that scroll by on the screen. These are normal and can safely be ignored. 47 These warnings are as they appear—warnings about deprecated, but not 48 invalid, use of the C or C++ syntax. C standards change fairly often, and 49 some packages still use the older standard. This is not a problem, but does 50 prompt the warning.</para> 55 51 56 <para>Check one last time that the <envar>LFS</envar> environment 57 variable is set up properly:</para> 52 <important> 53 <para>After installing each package, delete its source and build directories, 54 unless specifically instructed otherwise. Deleting the sources prevents 55 mis-configuration when the same package is reinstalled later. Only three 56 of the packages need to retain the source and build directories in order 57 for their contents to be used by later commands. Pay special attention to 58 these reminders.</para> 59 </important> 60 61 <para>Check one last time that the <envar>LFS</envar> environment 62 variable is set up properly:</para> 58 63 59 64 <screen role="nodump"><userinput>echo $LFS</userinput></screen> 60 65 61 <para>Make sure the output shows the path to the LFS partition's mount62 point, which is <filename class="directory">/mnt/lfs</filename>, using63 our example.</para>66 <para>Make sure the output shows the path to the LFS partition's mount 67 point, which is <filename class="directory">/mnt/lfs</filename>, using 68 our example.</para> 64 69 65 70 </sect1> 66
Note:
See TracChangeset
for help on using the changeset viewer.
