From 443cace8ce11238d6509c09ba9f3d7f7901d2d4b Mon Sep 17 00:00:00 2001 From: Greg Schafer Date: Sat, 17 Jan 2004 01:37:37 +0000 Subject: Implemented changes to make the running of the Chapter 5 test suites strictly optional i.e. the default action for the average reader is to not run them. Closes 719. git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@3172 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689 --- chapter05/gcc-pass1.xml | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) (limited to 'chapter05/gcc-pass1.xml') 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; Unpack only the GCC-core tarball, as we won't be needing a C++ compiler for the moment. -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. - 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. +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. + And install the package: make install -- cgit v1.2.3-54-g00ecf