source: chapter06/introduction.xml@ 148bb04

10.0 10.0-rc1 10.1 10.1-rc1 11.0 11.0-rc1 11.0-rc2 11.0-rc3 11.1 11.1-rc1 11.2 11.2-rc1 11.3 11.3-rc1 12.0 12.0-rc1 12.1 12.1-rc1 6.0 6.1 6.1.1 6.3 6.4 6.5 6.6 6.7 6.8 7.0 7.1 7.2 7.3 7.4 7.5 7.5-systemd 7.6 7.6-systemd 7.7 7.7-systemd 7.8 7.8-systemd 7.9 7.9-systemd 8.0 8.1 8.2 8.3 8.4 9.0 9.1 arm bdubbs/gcc13 ml-11.0 multilib renodr/libudev-from-systemd s6-init trunk v5_0 v5_1 v5_1_1 xry111/arm64 xry111/arm64-12.0 xry111/clfs-ng xry111/lfs-next xry111/loongarch xry111/loongarch-12.0 xry111/loongarch-12.1 xry111/mips64el xry111/pip3 xry111/rust-wip-20221008 xry111/update-glibc
Last change on this file since 148bb04 was 148bb04, checked in by Alex Gronenwoud <alex@…>, 21 years ago

Renaming /stage1 to /tools.

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2725 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

  • Property mode set to 100644
File size: 1.7 KB
Line 
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
6constructing our LFS system in earnest. That is, we chroot into
7our temporary mini Linux system, create some auxiliary things,
8and then start installing all the packages, one by one.</para>
9
10<para>The installation of all this software is pretty straightforward,
11and you will probably think it would be much shorter to give here
12the generic installation instructions and explain in full only the
13installation of those packages that require an alternate method.
14Although we agree with that, we nevertheless choose to give the
15full instructions for each and every package, simply to minimize
16the possibilities for mistakes.</para>
17
18<para>If you plan to use compiler optimizations in this chapter,
19take a look at the optimization hint at
20<ulink url="&hints-root;optimization.txt"/>.
21Compiler optimizations can make a program run faster, but they
22may also cause compilation difficulties. If a package refuses
23to compile when using optimization, try to compile it without
24optimization and see if the problem goes away.</para>
25
26<para>The order in which packages are installed in this chapter has
27to be strictly followed, to ensure that no program gets a path referring
28to <filename class="directory">/tools</filename> hard-wired into it.
29For the same reason, <emphasis>do not </emphasis> compile packages
30in parallel. Compiling in parallel may save you some time (especially on
31dual-CPU machines), but it could result in a program containing a
32hard-wired path to <filename class="directory">/tools</filename>,
33which will cause the program to stop working when the static directory
34is removed.</para>
35
36</sect1>
37
Note: See TracBrowser for help on using the repository browser.