1 | <?xml version="1.0" encoding="ISO-8859-1"?>
|
---|
2 | <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
|
---|
3 | "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
|
---|
4 | <!ENTITY % general-entities SYSTEM "../general.ent">
|
---|
5 | %general-entities;
|
---|
6 | ]>
|
---|
7 |
|
---|
8 | <sect1 id="ch-tools-introduction">
|
---|
9 | <?dbhtml filename="introduction.html"?>
|
---|
10 |
|
---|
11 | <title>Introduction</title>
|
---|
12 |
|
---|
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>
|
---|
17 |
|
---|
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>
|
---|
22 |
|
---|
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>
|
---|
28 |
|
---|
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>
|
---|
36 |
|
---|
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>
|
---|
44 |
|
---|
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>
|
---|
51 |
|
---|
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.</para>
|
---|
56 | </important>
|
---|
57 |
|
---|
58 | <para>Check one last time that the <envar>LFS</envar> environment
|
---|
59 | variable is set up properly:</para>
|
---|
60 |
|
---|
61 | <screen role="nodump"><userinput>echo $LFS</userinput></screen>
|
---|
62 |
|
---|
63 | <para>Make sure the output shows the path to the LFS partition's mount
|
---|
64 | point, which is <filename class="directory">/mnt/lfs</filename>, using
|
---|
65 | our example.</para>
|
---|
66 |
|
---|
67 | </sect1>
|
---|