diff options
Diffstat (limited to 'chapter05/gcc-pass1.xml')
| -rw-r--r-- | chapter05/gcc-pass1.xml | 13 |
1 files changed, 8 insertions, 5 deletions
diff --git a/chapter05/gcc-pass1.xml b/chapter05/gcc-pass1.xml index 6a83e9089..2ec21c6d3 100644 --- a/chapter05/gcc-pass1.xml +++ b/chapter05/gcc-pass1.xml @@ -18,11 +18,6 @@ Estimated required disk space: &gcc-compsize-tools-pass1;</screen> <para>Unpack only the GCC-core tarball, as we won't be needing a C++ compiler for the moment.</para> -<note><para>Even though GCC is an important toolchain package, we are not -going to run the test suite at this early stage. First, the test suite framework -is not yet in place and second, the programs from this first pass will soon be -overwritten by those installed in the second pass.</para></note> - <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 @@ -83,6 +78,14 @@ 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>And install the package:</para> <screen><userinput>make install</userinput></screen> |