diff --git a/chapter05/binutils-pass2-inst.xml b/chapter05/binutils-pass2-inst.xml index f660d334d..6184fc1ac 100644 --- a/chapter05/binutils-pass2-inst.xml +++ b/chapter05/binutils-pass2-inst.xml @@ -4,7 +4,7 @@ Re-installation of Binutils It's worth pointing out that the Binutils test suite we run in this -section is considered not as critical as the one we run in Chapter 6. +section is considered not as important as the one we run in Chapter 6. Create a separate build directory again: diff --git a/chapter05/gcc-pass2-inst.xml b/chapter05/gcc-pass2-inst.xml index 02f342f5c..74ef57c8c 100644 --- a/chapter05/gcc-pass2-inst.xml +++ b/chapter05/gcc-pass2-inst.xml @@ -25,7 +25,7 @@ are able to resolve the issue. You can consult the LFS Wiki at get PTYs working. It's worth pointing out that the GCC test suite we run in this -section is considered not as critical as the one we run in Chapter 6. +section is considered not as important as the one we run in Chapter 6. Unpack all three GCC tarballs (-core, -g++, and -testsuite) in one and the same working directory. They will all unfold into a single gcc-&gcc-version;/ @@ -77,9 +77,15 @@ variables that override the default optimization flags. Compile the package: make + There is no need to use the bootstrap target now, -as the compiler we're using to compile this GCC has been built from the exact -same sources. +as the compiler we're using to compile this GCC was built from the exact same +version of the GCC sources we used earlier. + +At this point it is strongly recommended to repeat the sanity check +we performed earlier in the chapter. Refer back to the "Locking in" Glibc section +and repeat the check. If the results are wrong then most likely, you forgot to +apply the abovementioned GCC Specs patch. Test the results: diff --git a/chapter05/glibc-inst.xml b/chapter05/glibc-inst.xml index 502699145..a55dcf2d8 100644 --- a/chapter05/glibc-inst.xml +++ b/chapter05/glibc-inst.xml @@ -10,7 +10,7 @@ you would normally do. We are going to run the test suite for Glibc in this chapter. However, it's worth pointing out that the Glibc test suite we run in this -section is considered not as critical as the one we run in Chapter 6. +section is considered not as important as the one we run in Chapter 6. This package is known to behave badly when you have changed its default optimization flags (including the -march and -mcpu options).