1 | <?xml version="1.0" encoding="ISO-8859-1"?>
|
---|
2 | <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
|
---|
3 | "http://www.oasis-open.org/docbook/xml/4.5/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 os="a">In this chapter, we use the cross-compile tools to build
|
---|
14 | the final CLFS system. The installation of this software is
|
---|
15 | straightforward. Although in many cases the installation instructions
|
---|
16 | could be made shorter and more generic, we have opted to provide the full
|
---|
17 | instructions for every package to minimize the possibilities for mistakes.
|
---|
18 | The key to learning what makes a Linux system work is to know what each
|
---|
19 | package is used for and why the user (or the system) needs it. For every
|
---|
20 | installed package, a summary of its contents is given, followed by concise
|
---|
21 | descriptions of each program and library the package installed.</para>
|
---|
22 |
|
---|
23 | <para os="b">If using compiler optimizations, please review the
|
---|
24 | optimization hint at <ulink url="&hints-root;optimization.txt"/>.
|
---|
25 | Compiler optimizations can make a program run slightly faster, but
|
---|
26 | they may also cause compilation difficulties and problems when
|
---|
27 | running the program. If a package refuses to compile when using
|
---|
28 | optimization, try to compile it without optimization and see if
|
---|
29 | that fixes the problem. Even if the package
|
---|
30 | does compile when using optimization, there is the risk it may have
|
---|
31 | been compiled incorrectly because of the complex interactions between
|
---|
32 | the code and build tools. Also note that the <option>-march</option>
|
---|
33 | and <option>-mtune</option> options may cause problems with the toolchain
|
---|
34 | packages (Binutils, GCC and Glibc). The small potential gains achieved in
|
---|
35 | using compiler optimizations are often outweighed by the risks. First-time
|
---|
36 | builders of CLFS are encouraged to build without custom optimizations.
|
---|
37 | The subsequent system will still run very fast and be stable at the
|
---|
38 | same time.</para>
|
---|
39 |
|
---|
40 | <para os="c">The order that packages are installed in this chapter needs to
|
---|
41 | be strictly followed to ensure that all package dependencies are
|
---|
42 | fulfilled.</para>
|
---|
43 |
|
---|
44 | <para os="d">To keep track of which package installs particular files, a
|
---|
45 | package manager can be used. For a general overview of different styles of
|
---|
46 | package managers, please take a look at the next page.</para>
|
---|
47 |
|
---|
48 | </sect1>
|
---|