diff options
Diffstat (limited to 'chapter05')
| -rw-r--r-- | chapter05/chapter05.xml | 1 | ||||
| -rw-r--r-- | chapter05/generalinstructions.xml | 71 | ||||
| -rw-r--r-- | chapter05/introduction.xml | 40 |
3 files changed, 73 insertions, 39 deletions
diff --git a/chapter05/chapter05.xml b/chapter05/chapter05.xml index 5fa82f6da..5d776d032 100644 --- a/chapter05/chapter05.xml +++ b/chapter05/chapter05.xml @@ -13,6 +13,7 @@ <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="introduction.xml"/> <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="toolchaintechnotes.xml"/> + <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="generalinstructions.xml"/> <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="binutils-pass1.xml"/> <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="gcc-pass1.xml"/> <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="linux-headers.xml"/> diff --git a/chapter05/generalinstructions.xml b/chapter05/generalinstructions.xml new file mode 100644 index 000000000..bab8bed22 --- /dev/null +++ b/chapter05/generalinstructions.xml @@ -0,0 +1,71 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" + "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ + <!ENTITY % general-entities SYSTEM "../general.ent"> + %general-entities; +]> + +<sect1 id="ch-tools-generalinstructions"> + <?dbhtml filename="generalinstructions.html"?> + + <title>General Compilation Instructions</title> + + <para>When building packages there are several assumptions made within + the instructions:</para> + + <itemizedlist> + + <listitem> + <para>Several of the packages are patched before compilation, but only when + the patch is needed to circumvent a problem. A patch is often needed in + both this and the next chapter, but sometimes in only one or the other. + Therefore, do not be concerned if instructions for a downloaded patch seem + to be missing. Warning messages about <emphasis>offset</emphasis> or + <emphasis>fuzz</emphasis> may also be encountered when applying a patch. Do + not worry about these warnings, as the patch was still successfully + applied.</para> + </listitem> + + <listitem> + <para>During the compilation of most packages, there will be several + warnings that scroll by on the screen. These are normal and can safely be + ignored. These warnings are as they appear—warnings about + deprecated, but not invalid, use of the C or C++ syntax. C standards change + fairly often, and some packages still use the older standard. This is not a + problem, but does prompt the warning.</para> + + <important> + <para>After installing each package, delete its source and build + directories, unless specifically instructed otherwise. Deleting the + sources prevents mis-configuration when the same package is reinstalled + later.</para> + </important> + </listitem> + + <listitem> + <para>Check one last time that the <envar>LFS</envar> environment variable + is set up properly:</para> + +<screen role="nodump"><userinput>echo $LFS</userinput></screen> + + <para>Make sure the output shows the path to the LFS partition's mount + point, which is <filename class="directory">/mnt/lfs</filename>, using our + example.</para> + </listitem> + + <listitem> + + <para>Finally, one last important item must be emphasized:</para> + + <important> + <para>Before issuing the build instructions for a package, the package + should be unpacked as user <systemitem class="username">lfs</systemitem>, + and a <command>cd</command> into the created directory should be + performed. The build instructions assume that the + <command>bash</command> shell is in use.</para> + </important> + </listitem> + + </itemizedlist> + +</sect1> diff --git a/chapter05/introduction.xml b/chapter05/introduction.xml index 5e6a17119..33a566877 100644 --- a/chapter05/introduction.xml +++ b/chapter05/introduction.xml @@ -10,7 +10,7 @@ <title>Introduction</title> - <para>This chapter shows how to compile and install a minimal Linux system. + <para>This chapter shows how to build a minimal Linux system. This system will contain just enough tools to start constructing the final LFS system in <xref linkend="chapter-building-system"/> and allow a working environment with more user convenience than a minimum environment would.</para> @@ -26,42 +26,4 @@ production directories. Since the packages compiled here are temporary, we do not want them to pollute the soon-to-be LFS system.</para> - <important> - <para>Before issuing the build instructions for a package, the package - should be unpacked as user <systemitem class="username">lfs</systemitem>, - and a <command>cd</command> into the created directory should be performed. - The build instructions assume that the <command>bash</command> shell is - in use.</para> - </important> - - <para>Several of the packages are patched before compilation, but only when - the patch is needed to circumvent a problem. A patch is often needed in both - this and the next chapter, but sometimes in only one or the other. Therefore, - do not be concerned if instructions for a downloaded patch seem to be missing. - Warning messages about <emphasis>offset</emphasis> or <emphasis>fuzz</emphasis> - may also be encountered when applying a patch. Do not worry about these - warnings, as the patch was still successfully applied.</para> - - <para>During the compilation of most packages, there will be several warnings - that scroll by on the screen. These are normal and can safely be ignored. - These warnings are as they appear—warnings about deprecated, but not - invalid, use of the C or C++ syntax. C standards change fairly often, and - some packages still use the older standard. This is not a problem, but does - prompt the warning.</para> - - <important> - <para>After installing each package, delete its source and build directories, - unless specifically instructed otherwise. Deleting the sources prevents - mis-configuration when the same package is reinstalled later.</para> - </important> - - <para>Check one last time that the <envar>LFS</envar> environment - variable is set up properly:</para> - -<screen role="nodump"><userinput>echo $LFS</userinput></screen> - - <para>Make sure the output shows the path to the LFS partition's mount - point, which is <filename class="directory">/mnt/lfs</filename>, using - our example.</para> - </sect1> |