|
|
@@ -10,8 +10,7 @@ the gcc-core tarball needs to be unpacked at this time.</para>
|
|
|
default optimization flags (including the -march and -mcpu options). GCC is
|
|
|
best left alone. Therefore, if you have defined any environment variables
|
|
|
that override default optimizations, such as CFLAGS and CXXFLAGS, we
|
|
|
-recommend unsetting or modifying them when building GCC. You have
|
|
|
-been warned.</para>
|
|
|
+recommend unsetting or modifying them when building GCC.</para>
|
|
|
|
|
|
<para>It is recommended by the GCC installation documentation to build
|
|
|
GCC outside of the source directory in a dedicated directory:</para>
|
|
|
@@ -32,7 +31,8 @@ cd ../gcc-build</userinput></screen></para>
|
|
|
<listitem><para><userinput>--prefix=/static:</userinput> This is NOT a
|
|
|
typo. GCC hard codes some paths while compiling and so we need to pass
|
|
|
<filename class="directory">/static</filename> as the prefix during the
|
|
|
-configure stage. We pass the real install prefix during the installation
|
|
|
+configure stage. We will pass the real installation prefix (<filename
|
|
|
+class="directory">$LFS/static</filename> during the installation
|
|
|
stage later on.</para></listitem>
|
|
|
|
|
|
<listitem><para><userinput>--disable-shared:</userinput> This prevents the
|
|
|
@@ -82,7 +82,7 @@ If so, it will fix them and put them in
|
|
|
<filename>$LFS/static/lib/gcc-lib/i686-pc-linux-gnu/3.2</filename>. Later on
|
|
|
in chapter 6 you will install Glibc which will put its header files in
|
|
|
<filename>/usr/include</filename>. Next you will install other programs that
|
|
|
-use the Glibc headers. GCC will look in
|
|
|
+use the Glibc headers and GCC will look in
|
|
|
<filename>/static/lib/gcc-lib</filename> before looking in
|
|
|
<filename>/usr/include</filename>, with the result of finding and using the
|
|
|
fixed Glibc header files from your host distribution, which are probably
|
Gerard Beekmans