Changeset 44c2fd8 for chapter06/introduction.xml
- Timestamp:
- 09/08/2002 09:54:14 PM (22 years ago)
- Branches:
- 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, v4_0, v4_1, 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
- Children:
- e9d69fa6
- Parents:
- cb33ea8
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter06/introduction.xml
rcb33ea8 r44c2fd8 8 8 and then start installing all the packages, one by one.</para> 9 9 10 <para>The installation of all th e software is pretty straightforward, and11 you will probably think it would be so much easier and shorter to give12 the generic installation instructions for a package here and only explain13 in full the installation of those packages that require an alternate14 method. Although we agree with that, wechoose to give the15 full instructions for each and every package, simply to avoid any16 possible confusion and errors.</para>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 17 18 <para>If you plan to use compiler optimization for the packages19 installed in this chapter, take a look at the optimization hint 20 at<ulink url="&hints-root;optimization.txt"/>.21 Compiler optimization can make a program run22 faster, but may also cause compilation problems. If you run into problems23 when using optimization, always try it without optimization to see if 24 the problem persists.</para>18 <para>If you plan to use compiler optimizations in this chapter, 19 take a look at the optimization hint at 20 <ulink url="&hints-root;optimization.txt"/>. 21 Compiler optimizations can make a program run faster, but they 22 may also cause compilation difficulties. If a package refuses 23 to compile when using optimization, try to compile it without 24 optimization and see if the problem goes away.</para> 25 25 26 <para>Please refrain from installing more than one package at a time, even 27 if it may save you time (especially with dual CPU machines). If you install 28 the wrong package at the wrong time, it may hard-wire program paths to 29 <filename class="directory">$LFS/static</filename> which will cause the 30 programs to stop working once the static directory is removed. The order 31 packages are installed in this chapter have to be followed exactly to be 32 sure nothing is hard-wiring the static paths.</para> 26 <para>The order in which packages are installed in this chapter has 27 to be strictly followed, to ensure that no program gets a path referring 28 to <filename class="directory">/static</filename> hard-wired into it. 29 For the same reason, <emphasis>do not </emphasis> compile packages 30 in parallel. Compiling in parallel may save you some time (especially on 31 dual-CPU machines), but it could result in a program containing a 32 hard-wired path to <filename class="directory">/static</filename>, 33 which will cause the program to stop working when the static directory 34 is removed.</para> 33 35 34 36 </sect1>
Note:
See TracChangeset
for help on using the changeset viewer.