diff options
author | Manuel Canales Esparcia <manuel@linuxfromscratch.org> | 2004-05-30 13:41:04 +0000 |
---|---|---|
committer | Manuel Canales Esparcia <manuel@linuxfromscratch.org> | 2004-05-30 13:41:04 +0000 |
commit | 574b0eabcc0015a1ee7c8b7098f50e2b6b0e9005 (patch) | |
tree | 83d15d25797db1a7575a6bc2e8b8d34783f25e14 /chapter05/gcc-pass1.xml | |
parent | b711e1d6218396e587b111d540c8567453b21502 (diff) |
Tagging corrections in chapters 5.
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@3730 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Diffstat (limited to 'chapter05/gcc-pass1.xml')
-rw-r--r-- | chapter05/gcc-pass1.xml | 20 |
1 files changed, 10 insertions, 10 deletions
diff --git a/chapter05/gcc-pass1.xml b/chapter05/gcc-pass1.xml index 21f71878e..3f43d67bf 100644 --- a/chapter05/gcc-pass1.xml +++ b/chapter05/gcc-pass1.xml @@ -31,8 +31,8 @@ nor the test suite here.</para> <para>This package is known to behave badly when you change its default -optimization flags (including the <emphasis>-march</emphasis> and -<emphasis>-mcpu</emphasis> options). Therefore, if you have defined any +optimization flags (including the <parameter>-march</parameter> and +<parameter>-mcpu</parameter> options). Therefore, if you have defined any environment variables that override default optimizations, such as CFLAGS and CXXFLAGS, we recommend un-setting them when building GCC.</para> @@ -52,27 +52,27 @@ cd ../gcc-build</userinput></screen> <variablelist> <varlistentry> -<term><userinput>--with-local-prefix=/tools</userinput></term> -<listitem><para>The purpose of this switch is to remove <filename>/usr/local/include</filename> +<term><parameter>--with-local-prefix=/tools</parameter></term> +<listitem><para>The purpose of this switch is to remove <filename class="directory">/usr/local/include</filename> from <command>gcc</command>'s include search path. This is not absolutely essential; however, we want to try to minimize the influence of the host system, so this a sensible thing to do.</para></listitem> </varlistentry> <varlistentry> -<term><userinput>--enable-shared</userinput></term> +<term><parameter>--enable-shared</parameter></term> <listitem><para>This switch may seem counter-intuitive at first. But using it allows the building of <filename>libgcc_s.so.1</filename> and <filename>libgcc_eh.a</filename>, and having <filename>libgcc_eh.a</filename> available ensures that the configure script for Glibc (the next package we compile) produces the proper results. -Note that the <command>gcc</command> binaries will still be linked -statically, as this is controlled by the <emphasis>-static</emphasis> +Note that the GCC binaries will still be linked +statically, as this is controlled by the <parameter>-static</parameter> value of BOOT_LDFLAGS in the next step.</para></listitem> </varlistentry> <varlistentry> -<term><userinput>--enable-languages=c</userinput></term> +<term><parameter>--enable-languages=c</parameter></term> <listitem><para>This option ensures that only the C compiler is built. The option is only needed when you have downloaded and unpacked the full GCC tarball.</para></listitem> @@ -87,12 +87,12 @@ have downloaded and unpacked the full GCC tarball.</para></listitem> <variablelist> <varlistentry> -<term><userinput>BOOT_LDFLAGS="-static"</userinput></term> +<term><parameter>BOOT_LDFLAGS="-static"</parameter></term> <listitem><para>This tells GCC to link its programs statically.</para></listitem> </varlistentry> <varlistentry> -<term><userinput>bootstrap</userinput></term> +<term><parameter>bootstrap</parameter></term> <listitem><para>This target doesn't just compile GCC, but compiles it several times. It uses the programs compiled in a first round to compile itself a second time, and then again a third time. |