diff options
| author | Greg Schafer <greg@linuxfromscratch.org> | 2003-09-26 04:11:08 +0000 |
|---|---|---|
| committer | Greg Schafer <greg@linuxfromscratch.org> | 2003-09-26 04:11:08 +0000 |
| commit | 1cb7ced1c435847432511e06989b1d650912d921 (patch) | |
| tree | 09e8eafec67f9871dc0456709f8955f07bfdd496 /chapter06 | |
| parent | 6952b96fa29f30559ef1ac6d17f630ea2efc007a (diff) | |
Small fixups across the board.
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2883 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Diffstat (limited to 'chapter06')
| -rw-r--r-- | chapter06/chroot.xml | 2 | ||||
| -rw-r--r-- | chapter06/introduction.xml | 18 |
2 files changed, 12 insertions, 8 deletions
diff --git a/chapter06/chroot.xml b/chapter06/chroot.xml index 15e7894cd..cd45f41a3 100644 --- a/chapter06/chroot.xml +++ b/chapter06/chroot.xml @@ -27,7 +27,7 @@ like vim and less to operate properly. If you need other variables present, such as CFLAGS or CXXFLAGS, this is a good place to set them again.</para> <para>Also note the use of the set +h directive. This tells bash to not use -it's internal path hashing. Without this directive, bash will remember paths +its internal path hashing. Without this directive, bash will remember paths to binaries. Since as we go thru chapter 6, we want to use our newly compiled binaries as soon as they are installed, we turn off this function.</para> diff --git a/chapter06/introduction.xml b/chapter06/introduction.xml index f8063525f..d04afa665 100644 --- a/chapter06/introduction.xml +++ b/chapter06/introduction.xml @@ -15,13 +15,17 @@ Although we agree with that, we nevertheless choose to give the full instructions for each and every package, simply to minimize the possibilities for mistakes.</para> -<para>If you plan to use compiler optimizations in this chapter, -take a look at the optimization hint at -<ulink url="&hints-root;optimization.txt"/>. -Compiler optimizations can make a program run faster, but they -may also cause compilation difficulties. If a package refuses -to compile when using optimization, try to compile it without -optimization and see if the problem goes away.</para> +<para>If you plan to use compiler optimizations in this chapter, take a look at +the optimization hint at <ulink url="&hints-root;optimization.txt"/>. Compiler +optimizations can make a program run a touch faster, but they may also cause +compilation difficulties and even problems when running the program. If a +package refuses to compile when using optimization, try to compile it without +optimization and see if the problem goes away. Even if the package does compile +when using optimization, there is the risk it may have been compiled +incorrectly due to compiler bugs or whatever. In short, the small gains achieved +in using compiler optimization are generally outweighed by the risk. First time +builders of LFS are encouraged not to bother. Your system will still be plenty +fast enough and very stable at the same time.</para> <para>The order in which packages are installed in this chapter has to be strictly followed, to ensure that no program gets a path referring |