diff options
Diffstat (limited to 'chapter05/adjusting.xml')
| -rw-r--r-- | chapter05/adjusting.xml | 16 |
1 files changed, 12 insertions, 4 deletions
diff --git a/chapter05/adjusting.xml b/chapter05/adjusting.xml index 302c1e1cd..74098b7a3 100644 --- a/chapter05/adjusting.xml +++ b/chapter05/adjusting.xml @@ -61,10 +61,18 @@ dynamic linker in the above commands. Refer back to <xref linkend="ch-tools-toolchaintechnotes" role=","/> if necessary.</para></important> -<para>There is a possibility that some header files from the host system have -found their way into GCC's private include dir. This can happen as a result of -GCC's <quote>fixincludes</quote> process, which runs as part of the GCC build. -This is explained in more detail later in this chapter. Run the following commands to remove those header files (you may find it easier to copy and paste these commands, rather than typing them by hand, due to their length):</para> +<para>During the build process, GCC runs a script +(<command>fixincludes</command>) that scans the system for header files that may +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 +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 +remove the header files in GCC's private include directory (you may find it +easier to copy and paste these commands, rather than typing them by hand, due to +their length):</para> <!-- && used to ease copy and pasting --> <screen><userinput>GCC_INCLUDEDIR=`dirname $(gcc -print-libgcc-file-name)`/include && |