diff options
| author | Greg Schafer <greg@linuxfromscratch.org> | 2004-01-17 01:37:37 +0000 |
|---|---|---|
| committer | Greg Schafer <greg@linuxfromscratch.org> | 2004-01-17 01:37:37 +0000 |
| commit | 443cace8ce11238d6509c09ba9f3d7f7901d2d4b (patch) | |
| tree | 59a6342f69e5a56a69b66b0e23d4311022947a95 /chapter05/binutils-pass1.xml | |
| parent | b05a83179d382145b6c1c8ae566870fac5ed84cb (diff) | |
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
Diffstat (limited to 'chapter05/binutils-pass1.xml')
| -rw-r--r-- | chapter05/binutils-pass1.xml | 13 |
1 files changed, 8 insertions, 5 deletions
diff --git a/chapter05/binutils-pass1.xml b/chapter05/binutils-pass1.xml index db33530f5..43c99423a 100644 --- a/chapter05/binutils-pass1.xml +++ b/chapter05/binutils-pass1.xml @@ -17,11 +17,6 @@ Estimated required disk space: &binutils-compsize-tools-pass1;</screen> because both Glibc and GCC perform various tests on the available linker and assembler to determine which of their own features to enable.</para> -<note><para>Even though Binutils 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 default @@ -77,6 +72,14 @@ strictly speaking, <userinput>"-all-static"</userinput> is first passed to the <userinput>"-static"</userinput> on to the linker.</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 Binutils 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> |