|
@@ -28,19 +28,19 @@ cd ../gcc-build</userinput></screen></para>
|
|
|
<para>The meaning of the configure options are:</para>
|
|
|
|
|
|
<itemizedlist>
|
|
|
-<listitem><para><userinput>--prefix=/static:</userinput> This is NOT a
|
|
|
+<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 will pass the real installation prefix (<filename
|
|
|
-class="directory">$LFS/static</filename> during the installation
|
|
|
+class="directory">$LFS/static</filename>) during the installation
|
|
|
stage later on.</para></listitem>
|
|
|
|
|
|
-<listitem><para><userinput>--disable-shared:</userinput> This prevents the
|
|
|
+<listitem><para><userinput>--disable-shared</userinput>: This prevents the
|
|
|
build of dynamic libraries. They are useless to us at the moment. We'll
|
|
|
create them when we reinstall GCC in chapter 6.</para></listitem>
|
|
|
|
|
|
<listitem><para><userinput>--with-as=$LFS/static/bin/as and
|
|
|
---with-ld=$LFS/static/bin/ld:</userinput> GCC can be miscompiled if your
|
|
|
+--with-ld=$LFS/static/bin/ld</userinput>: GCC can be miscompiled if your
|
|
|
host distribution's Binutils package is quite old. We need a good working
|
|
|
static GCC until we reinstall GCC later in chapter 6. So by using
|
|
|
<filename>as</filename> and <filename>ld</filename> from the Binutils
|
|
@@ -55,14 +55,14 @@ correctly.</para></listitem>
|
|
|
<para>The meaning of the make options are:</para>
|
|
|
|
|
|
<itemizedlist>
|
|
|
-<listitem><para><userinput>BOOT_LDFLAGS="-static":</userinput> This is
|
|
|
+<listitem><para><userinput>BOOT_LDFLAGS="-static"</userinput>: This is
|
|
|
GCC's equivalent to make LDFLAGS="-static" as we use with other packages to
|
|
|
compile them statically.</para></listitem>
|
|
|
|
|
|
-<listitem><para><userinput>bootstrap:</userinput> The
|
|
|
+<listitem><para><userinput>bootstrap</userinput>: The
|
|
|
<emphasis>bootstrap</emphasis> target doesn't just compile GCC, but it
|
|
|
compiles GCC a second time. It uses the first compiled programs to compile
|
|
|
-itself a second and third time to make sure the compiler compiled properly
|
|
|
+itself a second and third time to make sure the compiler was compiled properly
|
|
|
and can compile itself properly.</para></listitem>
|
|
|
</itemizedlist>
|
|
|
|
|
@@ -73,7 +73,7 @@ and can compile itself properly.</para></listitem>
|
|
|
<para>The meaning of the make option is:</para>
|
|
|
|
|
|
<itemizedlist>
|
|
|
-<listitem><para><userinput>install-no-fixedincludes:</userinput> This prevents
|
|
|
+<listitem><para><userinput>install-no-fixedincludes</userinput>: This prevents
|
|
|
the fixincludes script from running. Preventing this is necessary because
|
|
|
under normal circumstances the GCC installation will run the fixincludes
|
|
|
script which scans your system for header files that need to be fixed. It
|
|
@@ -95,8 +95,9 @@ class="symlink">$LFS/static/bin/cc</filename> symlink. A lot of programs
|
|
|
and scripts try to run <userinput>cc</userinput> instead of
|
|
|
<userinput>gcc</userinput> This is to keep programs generic and usable on
|
|
|
all kinds of Unix systems. Not everybody has GNU CC installed. Just running
|
|
|
-cc (C Compiler) leaves the user free to decide which C compiler to install.
|
|
|
-The symlink will point to the system's default compiler.</para>
|
|
|
+<userinput>cc</userinput> (C Compiler) leaves the user free to decide which
|
|
|
+C compiler to install. The symlink will point to the system's default
|
|
|
+compiler.</para>
|
|
|
|
|
|
<para><screen><userinput>ln -s gcc $LFS/static/bin/cc</userinput></screen></para>
|
|
|
|