[673b0d8] | 1 | <?xml version="1.0" encoding="ISO-8859-1"?>
|
---|
[1770019] | 2 | <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
|
---|
[673b0d8] | 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 |
|
---|
[81fd230] | 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>
|
---|
| 15 |
|
---|
| 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>
|
---|
| 20 |
|
---|
| 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>
|
---|
| 27 |
|
---|
| 28 | <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>
|
---|
| 32 |
|
---|
| 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>
|
---|
| 41 |
|
---|
| 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>
|
---|
| 48 |
|
---|
| 49 | <para>After installing each package, delete its source and build
|
---|
| 50 | directories, unless specifically instructed otherwise. Deleting the
|
---|
| 51 | sources saves space and prevents mis-configuration when the same
|
---|
| 52 | package is reinstalled later. Only three of the packages need to
|
---|
| 53 | retain the source and build directories in order for their contents to
|
---|
| 54 | be used by later commands. Pay special attention to these
|
---|
| 55 | reminders.</para>
|
---|
| 56 |
|
---|
| 57 | <para>Check one last time that the <envar>LFS</envar> environment
|
---|
| 58 | variable is set up properly:</para>
|
---|
| 59 |
|
---|
| 60 | <screen><userinput>echo $LFS</userinput></screen>
|
---|
| 61 |
|
---|
| 62 | <para>Make sure the output shows the path to the LFS partition's mount
|
---|
| 63 | point, which is <filename class="directory">/mnt/lfs</filename>, using
|
---|
| 64 | our example.</para>
|
---|
[673b0d8] | 65 |
|
---|
| 66 | </sect1>
|
---|
[81fd230] | 67 |
|
---|