From 2c094d60db777dce20fd4eccf4996299c2a0dfe0 Mon Sep 17 00:00:00 2001 From: Timothy Bauscher Date: Sat, 28 Sep 2002 21:08:29 +0000 Subject: Applied Bill Maltby's grammar patch. Changed $LFS to LFS where appropriate. Internal XML cleanup: removed double spacing where appropriate. git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2138 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689 --- chapter06/introduction.xml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'chapter06/introduction.xml') diff --git a/chapter06/introduction.xml b/chapter06/introduction.xml index dfe834c24..68456fc4e 100644 --- a/chapter06/introduction.xml +++ b/chapter06/introduction.xml @@ -3,7 +3,7 @@ In this chapter we enter the building site, and start -constructing our LFS system in earnest. That is, we chroot into +constructing our LFS system in earnest. That is, we chroot into our temporary mini Linux system, create some auxiliary things, and then start installing all the packages, one by one. @@ -21,13 +21,13 @@ take a look at the optimization hint at 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. +optimization and see if the problem goes away. The order in which packages are installed in this chapter has to be strictly followed, to ensure that no program gets a path referring to /static hard-wired into it. For the same reason, do not compile packages -in parallel. Compiling in parallel may save you some time (especially on +in parallel. Compiling in parallel may save you some time (especially on dual-CPU machines), but it could result in a program containing a hard-wired path to /static, which will cause the program to stop working when the static directory -- cgit v1.2.3-54-g00ecf