- Timestamp:
- 09/26/2003 04:11:08 AM (21 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, 12.2, 12.2-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/loongarch-12.2, xry111/mips64el, xry111/multilib, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
- Children:
- eea36593
- Parents:
- 6952b96
- Location:
- chapter06
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter06/chroot.xml
r6952b96 r1cb7ced 28 28 29 29 <para>Also note the use of the set +h directive. This tells bash to not use 30 it 's internal path hashing. Without this directive, bash will remember paths30 its internal path hashing. Without this directive, bash will remember paths 31 31 to binaries. Since as we go thru chapter 6, we want to use our newly compiled 32 32 binaries as soon as they are installed, we turn off this function.</para> -
chapter06/introduction.xml
r6952b96 r1cb7ced 16 16 the possibilities for mistakes.</para> 17 17 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> 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 a touch 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 25 incorrectly due to compiler bugs or whatever. In short, the small gains achieved 26 in using compiler optimization are generally outweighed by the risk. First time 27 builders of LFS are encouraged not to bother. Your system will still be plenty 28 fast enough and very stable at the same time.</para> 25 29 26 30 <para>The order in which packages are installed in this chapter has
Note:
See TracChangeset
for help on using the changeset viewer.