aboutsummaryrefslogtreecommitdiffstats
path: root/chapter05/introduction.xml
diff options
context:
space:
mode:
authorBruce Dubbs <bdubbs@linuxfromscratch.org>2008-10-26 17:47:52 +0000
committerBruce Dubbs <bdubbs@linuxfromscratch.org>2008-10-26 17:47:52 +0000
commit3c63868dde31929aadfb518d212ff81893714e5c (patch)
treef4dc8b463caa8881682740ac48baa11ceddf1e8a /chapter05/introduction.xml
parent33d608db5af282cc0e2d6cb38b453c9c6a9cf7df (diff)
Added a General Compilation Instructions section
immediatley before binutils. Essentially reordered the presentation that was in the Chapter 5 Introduction. git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@8704 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Diffstat (limited to 'chapter05/introduction.xml')
-rw-r--r--chapter05/introduction.xml40
1 files changed, 1 insertions, 39 deletions
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&mdash;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>