diff options
Diffstat (limited to 'chapter05/gcc-pass1.xml')
| -rw-r--r-- | chapter05/gcc-pass1.xml | 34 |
1 files changed, 15 insertions, 19 deletions
diff --git a/chapter05/gcc-pass1.xml b/chapter05/gcc-pass1.xml index 08822cbf0..6cb01b4fa 100644 --- a/chapter05/gcc-pass1.xml +++ b/chapter05/gcc-pass1.xml @@ -15,14 +15,14 @@ <sect2> <title>Installation of GCC</title> -<para>Unpack only the GCC-core tarball, as we won't be needing a C++ compiler -for the moment.</para> +<para>Unpack only the GCC-core tarball, as we won't be needing the C++ compiler +nor the test suite at the moment.</para> -<para>This package is known to behave badly when you have changed its -default optimization flags (including the -march and -mcpu options). -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.</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 +environment variables that override default optimizations, such as CFLAGS and +CXXFLAGS, we recommend unsetting them when building GCC.</para> <para>The GCC documentation recommends building GCC outside of the source directory in a dedicated build directory:</para> @@ -52,8 +52,8 @@ seem counter-intuitive at first. But using it allows the building of 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 <command>-static</command> -value of BOOT_LDFLAGS further on.</para></listitem> +statically, as this is controlled by the <emphasis>-static</emphasis> +value of BOOT_LDFLAGS in the next step.</para></listitem> <listitem><para><userinput>--enable-languages=c</userinput>: This option ensures that only the C compiler is built. The option is only needed when you @@ -78,21 +78,17 @@ reproduce itself flawlessly, which most probably means that it was compiled correctly.</para></listitem> </itemizedlist> -<para>Compilation is now complete. This is the point where we would normally -run the test suite. But as discussed earlier, we don't recommend running the -test suites for the temporary tools here in this chapter. However, even if we -still wanted to run the GCC test suite, we're unable do so at this early stage -because the test suite framework is not yet in place. Not only that, the -programs from this first pass will soon be overwritten by those installed in -the second pass.</para> +<para>Compilation is now complete, and at this point we would normally run the +test suite. But, as mentioned before, the test suite framework is not in place +yet. And there would be little point in running the tests anyhow, since the +programs from this first pass will soon be replaced.</para> <para>And install the package:</para> <screen><userinput>make install</userinput></screen> -<para>As a finishing touch we'll create the <filename -class="symlink">/tools/bin/cc</filename> symlink. Many programs and -scripts run <command>cc</command> instead of <command>gcc</command>, +<para>As a finishing touch we'll create a symlink. Many programs and scripts +run <command>cc</command> instead of <command>gcc</command>, a thing meant to keep programs generic and therefore usable on all kinds of Unix systems. Not everybody has the GNU C compiler installed. Simply running <command>cc</command> leaves the system administrator free to decide what |