source: chapter05/introduction.xml@ 11e9988

6.0
Last change on this file since 11e9988 was 2256873, checked in by Gerard Beekmans <gerard@…>, 20 years ago

Last edit round.

git-svn-id: http://svn.linuxfromscratch.org/LFS/branches/testing/BOOK@4265 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

  • Property mode set to 100644
File size: 3.2 KB
RevLine 
[673b0d8]1<?xml version="1.0" encoding="ISO-8859-1"?>
2<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
3 <!ENTITY % general-entities SYSTEM "../general.ent">
4 %general-entities;
5]>
6<sect1 id="ch-tools-introduction">
7<title>Introduction</title>
8<?dbhtml filename="introduction.html"?>
9
[6e41459]10<para>This chapter shows how to compile and install a minimal Linux
11system. This system will contain just enough tools to start
12constructing the final LFS system in <xref
13linkend="chapter-building-system"/> and allow a working environment
14with more user convenience than a minimum environment would.</para>
[673b0d8]15
[6e41459]16<para>There are two steps in building this minimal system. The first
17step is to build a new and host-independent toolchain (compiler,
18assembler, linker, libraries, and a few useful utilities). The second
19step uses this toolchain to build the other essential tools.</para>
[673b0d8]20
21<para>The files compiled in this chapter will be installed under the
[6e41459]22<filename class="directory">$LFS/tools</filename> directory to keep
23them separate from the files installed in the next chapter and the
24host production directories. Since the packages compiled here are
[69993f4]25temporary, we do not want them to pollute the soon-to-be LFS
[6e41459]26system.</para>
[673b0d8]27
[6e41459]28<para>Before issuing the build instructions for a package, the package
[82f5ee3]29should be unpacked as user <emphasis>lfs</emphasis>, and a
30<command>cd</command> into the created directory should be performed. The build
31instructions assume that the <command>bash</command> shell is in use.</para>
[673b0d8]32
[6e41459]33<para>Several of the packages are patched before compilation, but only
34when the patch is needed to circumvent a problem. A patch is often
35needed in both this and the next chapter, but sometimes in only one or
36the other. Therefore, do not be concerned if instructions for a downloaded
37patch seem to be missing. Warning messages about
38<emphasis>offset</emphasis> or <emphasis>fuzz</emphasis> may
39also be encountered when applying a patch. Do not worry about these
40warnings, as the patch was still successfully applied.</para>
[673b0d8]41
[6e41459]42<para>During the compilation of most packages, there will be several
43warnings that scroll by on the screen. These are normal and can safely
[2256873]44be ignored. These warnings are as they appear&mdash;warnings about
[6e41459]45deprecated, but not invalid, use of the C or C++ syntax. C standards
[69993f4]46change fairly often, and some packages still use the older standard.
47This is not a problem, but does prompt the warning.</para>
[673b0d8]48
[2256873]49<beginpage/>
50
[6e41459]51<para>After installing each package, delete its source and build
52directories, unless specifically instructed otherwise. Deleting the
53sources saves space and prevents mis-configuration when the same
[69993f4]54package is reinstalled later. Only three of the packages need to
[6e41459]55retain the source and build directories in order for their contents to
56be used by later commands. Pay special attention to these
57reminders.</para>
[673b0d8]58
[e097438]59<para>Check one last time that the <envar>LFS</envar> environment
60variable is set up properly:</para>
[673b0d8]61
62<screen><userinput>echo $LFS</userinput></screen>
63
[6e41459]64<para>Make sure the output shows the path to the LFS partition's mount
65point, which is <filename class="directory">/mnt/lfs</filename>, using
66our example.</para>
[673b0d8]67
68</sect1>
[6e41459]69
Note: See TracBrowser for help on using the repository browser.