diff options
Diffstat (limited to 'chapter05/gcc-pass2.xml')
| -rw-r--r-- | chapter05/gcc-pass2.xml | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/chapter05/gcc-pass2.xml b/chapter05/gcc-pass2.xml index 762ce0d17..314f88019 100644 --- a/chapter05/gcc-pass2.xml +++ b/chapter05/gcc-pass2.xml @@ -44,12 +44,12 @@ same working directory. They will all unfold into a single <screen><userinput>patch -Np1 -i ../&gcc-nofixincludes-patch; patch -Np1 -i ../&gcc-specs-patch;</userinput></screen> -<para>The first patch disables the GCC "fixincludes" script. We mentioned this +<para>The first patch disables the GCC "fixincludes" script. We mentioned this briefly earlier, but a slightly more in-depth explanation of the fixincludes -process is warranted here. Under normal circumstances, the GCC fixincludes -script scans your system for header files that need to be fixed. It might find +process is warranted here. Under normal circumstances, the GCC fixincludes +script scans your system for header files that need to be fixed. It might find that some Glibc header files on your host system need to be fixed, fix them and -put them in the GCC private include directory. Then, later on in +put them in the GCC private include directory. Then, later on in <xref linkend="chapter06"/>, after we've installed the newer Glibc, this private include directory would be searched before the system include directory, resulting in GCC finding the fixed headers from the host system, @@ -159,7 +159,7 @@ usually aware of them but haven't yet gotten around to fixing them. In short, unless your results are vastly different from those at the above URL, it is safe to continue on.</para> -<para>And finally install the package:</para> +<para>And finally install the package:</para> <screen><userinput>make install</userinput></screen> |