source: BOOK/final-system/common/introduction.xml @ 9f08378

Last change on this file since 9f08378 was 9f08378, checked in by Jim Gifford <clfs@…>, 18 years ago

r3564@server (orig r1629): chris | 2006-05-17 13:05:26 -0700
More text updates, mostly to change LFS references to CLFS

  • Property mode set to 100644
File size: 3.1 KB
1<?xml version="1.0" encoding="ISO-8859-1"?>
2<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
3  "" [
4  <!ENTITY % general-entities SYSTEM "../../general.ent">
5  %general-entities;
8<sect1 id="ch-system-introduction">
9  <?dbhtml filename="introduction.html"?>
11  <title>Introduction</title>
13  <para os="a">In this chapter, we enter the building site and start
14  constructing the CLFS system in earnest. The installation of this
15  software is straightforward. Although in many cases the installation
16  instructions could be made shorter and more generic, we have opted
17  to provide the full instructions for every package to minimize the
18  possibilities for mistakes.  The key to learning what makes a Linux
19  system work is to know what each package is used for and why the user
20  (or the system) needs it.  For every installed package, a summary of
21  its contents is given, followed by concise descriptions of each
22  program and library the package installed.</para>
24  <para os="b">If using the compiler optimizations provided in this chapter,
25  please review the optimization hint at <ulink
26  url="&hints-root;optimization.txt"/>.  Compiler optimizations can make
27  a program run slightly faster, but they may also cause compilation
28  difficulties and problems when running the program. If a package
29  refuses to compile when using optimization, try to compile it without
30  optimization and see if that fixes the problem. Even if the package
31  does compile when using optimization, there is the risk it may have
32  been compiled incorrectly because of the complex interactions between
33  the code and build tools.  Also note that the <option>-march</option>
34  and <option>-mtune</option> options may cause problems with the toolchain
35  packages (Binutils, GCC and Glibc). The small potential gains achieved in
36  using compiler optimizations are often outweighed by the risks. First-time
37  builders of CLFS are encouraged to build without custom optimizations.
38  The subsequent system will still run very fast and be stable at the
39  same time.</para>
41  <para os="c">The order that packages are installed in this chapter needs to
42  be strictly followed to ensure that no program accidentally acquires a
43  path referring to <filename class="directory">/tools</filename>
44  hard-wired into it. For the same reason, do not compile packages in
45  parallel. Compiling in parallel may save time (especially on dual-CPU
46  machines), but it could result in a program containing a hard-wired
47  path to <filename class="directory">/tools</filename>, which will
48  cause the program to stop working when that directory is
49  removed.</para>
51  <para os="d">Before the installation instructions, each installation
52  page provides a concise description of what the package contains.
53  Following the installation instructions, there is a list of programs
54  and libraries (along with brief descriptions of these) that the
55  package installs.</para>
57  <para os="e">To keep track of which package installs particular files, a
58  package manager can be used. For a general overview of different styles of
59  package managers, please take a look at the next page.</para>
Note: See TracBrowser for help on using the repository browser.