| 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-system-introduction">
|
|---|
| 9 | <?dbhtml filename="introduction.html"?>
|
|---|
| 10 |
|
|---|
| 11 | <title>Introduction</title>
|
|---|
| 12 |
|
|---|
| 13 | <para>In this chapter, we enter the building site and start constructing the
|
|---|
| 14 | LFS system in earnest. That is, we chroot into the temporary mini Linux system,
|
|---|
| 15 | make a few final preparations, and then begin installing the packages.</para>
|
|---|
| 16 |
|
|---|
| 17 | <para>The installation of this software is straightforward. Although in many
|
|---|
| 18 | cases the installation instructions could be made shorter and more generic,
|
|---|
| 19 | we have opted to provide the full instructions for every package to minimize
|
|---|
| 20 | the possibilities for mistakes. The key to learning what makes a Linux system
|
|---|
| 21 | work is to know what each package is used for and why the user (or the system)
|
|---|
| 22 | needs it. For every installed package, a summary of its contents is given,
|
|---|
| 23 | followed by concise descriptions of each program and library the package
|
|---|
| 24 | installed.</para>
|
|---|
| 25 |
|
|---|
| 26 | <para>If using compiler optimizations, please
|
|---|
| 27 | review the optimization hint at <ulink url="&hints-root;optimization.txt"/>.
|
|---|
| 28 | Compiler optimizations can make a program run slightly faster, but they may
|
|---|
| 29 | also cause compilation difficulties and problems when running the program.
|
|---|
| 30 | If a package refuses to compile when using optimization, try to compile it
|
|---|
| 31 | without optimization and see if that fixes the problem. Even if the package
|
|---|
| 32 | does compile when using optimization, there is the risk it may have been
|
|---|
| 33 | compiled incorrectly because of the complex interactions between the code
|
|---|
| 34 | and build tools. Also note that the <option>-march</option> and
|
|---|
| 35 | <option>-mtune</option> options may cause problems with the toolchain packages
|
|---|
| 36 | (Binutils, GCC and Glibc). The small potential gains achieved in using
|
|---|
| 37 | compiler optimizations are often outweighed by the risks. First-time builders
|
|---|
| 38 | of LFS are encouraged to build without custom optimizations. The subsequent
|
|---|
| 39 | system will still run very fast and be stable at the same time.</para>
|
|---|
| 40 |
|
|---|
| 41 | <para>The order that packages are installed in this chapter needs to be
|
|---|
| 42 | strictly followed to ensure that no program accidentally acquires a path
|
|---|
| 43 | referring to <filename class="directory">/tools</filename> hard-wired into
|
|---|
| 44 | it. For the same reason, do not compile packages in parallel. Compiling in
|
|---|
| 45 | parallel may save time (especially on dual-CPU machines), but it could result
|
|---|
| 46 | in a program containing a hard-wired path to <filename
|
|---|
| 47 | class="directory">/tools</filename>, which will cause the program to stop
|
|---|
| 48 | working when that directory is removed.</para>
|
|---|
| 49 |
|
|---|
| 50 | <para>Before the installation instructions, each installation page provides
|
|---|
| 51 | information about the package, including a concise description of what it
|
|---|
| 52 | contains, approximately how long it will take to build, and how much disk
|
|---|
| 53 | space is required during this building process. Following the installation
|
|---|
| 54 | instructions, there is a list of programs and libraries (along with brief
|
|---|
| 55 | descriptions of these) that the package installs.</para>
|
|---|
| 56 |
|
|---|
| 57 | </sect1>
|
|---|
