Chapter 5 - GCC Pass 2: Insert note to rerun the previously ran sanity check.

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2871 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

chapter05/binutils-pass2-inst.xml

@@ -4,7 +4,7 @@
 <title>Re-installation of Binutils</title>
 
 <note><para>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.</para>
+section is considered not as important as the one we run in Chapter 6.</para>
 </note>
 
 <para>Create a separate build directory again:</para>

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.</para>
 
 <note><para>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.</para></note>
+section is considered not as important as the one we run in Chapter 6.</para></note>
 
 <para>Unpack all three GCC tarballs (-core, -g++, and -testsuite) in one and the same working directory.
 They will all unfold into a single <filename>gcc-&gcc-version;/</filename>
@@ -77,9 +77,15 @@ variables that override the default optimization flags.</para>
 <para>Compile the package:</para>
 
 <para><screen><userinput>make</userinput></screen></para>
+
 <para>There is no need to use the <userinput>bootstrap</userinput> target now,
-as the compiler we're using to compile this GCC has been built from the exact
-same sources.</para>
+as the compiler we're using to compile this GCC was built from the exact same
+version of the GCC sources we used earlier.</para>
+
+<note><para>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.</para></note>
 
 <para>Test the results:</para>
 

chapter05/glibc-inst.xml

@@ -10,7 +10,7 @@ you would normally do.</para>
 
 <note><para>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.</para></note>
+section is considered not as important as the one we run in Chapter 6.</para></note>
 
 <para>This package is known to behave badly when you have changed its
 default optimization flags (including the -march and -mcpu options).