| 1 | <sect1 id="ch06-introduction">
|
|---|
| 2 | <title>Introduction</title>
|
|---|
| 3 | <?dbhtml filename="introduction.html" dir="chapter06"?>
|
|---|
| 4 |
|
|---|
| 5 | <para>In this chapter we enter the building site, and start
|
|---|
| 6 | constructing our LFS system in earnest. That is, we chroot into
|
|---|
| 7 | our temporary mini Linux system, create some auxiliary things,
|
|---|
| 8 | and then start installing all the packages, one by one.</para>
|
|---|
| 9 |
|
|---|
| 10 | <para>The installation of all this software is pretty straightforward,
|
|---|
| 11 | and you will probably think it would be much shorter to give here
|
|---|
| 12 | the generic installation instructions and explain in full only the
|
|---|
| 13 | installation of those packages that require an alternate method.
|
|---|
| 14 | Although we agree with that, we nevertheless choose to give the
|
|---|
| 15 | full instructions for each and every package, simply to minimize
|
|---|
| 16 | the possibilities for mistakes.</para>
|
|---|
| 17 |
|
|---|
| 18 | <para>If you plan to use compiler optimizations in this chapter, take a look at
|
|---|
| 19 | the optimization hint at <ulink url="&hints-root;optimization.txt"/>. Compiler
|
|---|
| 20 | optimizations can make a program run slightly faster, but they may also cause
|
|---|
| 21 | compilation difficulties and even problems when running the program. If a
|
|---|
| 22 | package refuses to compile when using optimization, try to compile it without
|
|---|
| 23 | optimization and see if the problem goes away. Even if the package does compile
|
|---|
| 24 | when using optimization, there is the risk it may have been compiled incorrectly
|
|---|
| 25 | due to complex interactions between the code and build tools. In short, the
|
|---|
| 26 | small potential gains achieved in using compiler optimization are generally
|
|---|
| 27 | outweighed by the risk. First time builders of LFS are encouraged to build
|
|---|
| 28 | without custom optimizations. Your system will still be very fast and very
|
|---|
| 29 | stable at the same time.</para>
|
|---|
| 30 |
|
|---|
| 31 | <para>The order in which packages are installed in this chapter has
|
|---|
| 32 | to be strictly followed, to ensure that no program gets a path referring
|
|---|
| 33 | to <filename class="directory">/tools</filename> hard-wired into it.
|
|---|
| 34 | For the same reason, <emphasis>do not </emphasis> compile packages
|
|---|
| 35 | in parallel. Compiling in parallel may save you some time (especially on
|
|---|
| 36 | dual-CPU machines), but it could result in a program containing a
|
|---|
| 37 | hard-wired path to <filename class="directory">/tools</filename>,
|
|---|
| 38 | which will cause the program to stop working when that directory
|
|---|
| 39 | is removed.</para>
|
|---|
| 40 |
|
|---|
| 41 | </sect1>
|
|---|
| 42 |
|
|---|
