diff options
author | Matthew Burgess <matthew@linuxfromscratch.org> | 2005-10-05 19:17:53 +0000 |
---|---|---|
committer | Matthew Burgess <matthew@linuxfromscratch.org> | 2005-10-05 19:17:53 +0000 |
commit | 6bff9167356300090fc2d40fe36040887b8197dc (patch) | |
tree | 3f50d9568dfc4e02193a86b7a51f45606d0ca70a /chapter05 | |
parent | 814f5ec179aa12c49e77ae38faafe9302cb0721f (diff) |
Fix a couple of typos
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@6963 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Diffstat (limited to 'chapter05')
-rw-r--r-- | chapter05/adjusting.xml | 2 | ||||
-rw-r--r-- | chapter05/gcc-pass2.xml | 2 |
2 files changed, 2 insertions, 2 deletions
diff --git a/chapter05/adjusting.xml b/chapter05/adjusting.xml index 74098b7a3..bb66cda34 100644 --- a/chapter05/adjusting.xml +++ b/chapter05/adjusting.xml @@ -66,7 +66,7 @@ necessary.</para></important> need to be fixed (they might contain syntax errors, for example), and installs the fixed versions in a private include directory. There is a possibility that, as a result of this process, some header files from the host system have found -their way into GCC's private include dir. As the rest of this chapter only +their way into GCC's private include directory. As the rest of this chapter only requires the headers from GCC and Glibc, which have both been installed at this point, any "fixed" headers can safely be removed. This helps to avoid any host headers polluting the build environment. Run the following commands to diff --git a/chapter05/gcc-pass2.xml b/chapter05/gcc-pass2.xml index 904dff8db..998ef3659 100644 --- a/chapter05/gcc-pass2.xml +++ b/chapter05/gcc-pass2.xml @@ -62,7 +62,7 @@ working.</para> normal circumstances the GCC <command>fixincludes</command> script is run in order to fix potentially broken header files. As GCC-&gcc-version; and Glibc-&glibc-version; have already been installed at this point, and their -respective header files are known not to require fixing, the +respective header files are known to not require fixing, the <command>fixincludes</command> script is not required. As mentioned previously, the script may in fact pollute the build environment by installing fixed headers from the host system into GCC's private include directory. The running of the |