Add sanity checks and some notes on the toolchain testsuites.

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

4 files changed, 38 insertions, 0 deletions

diff --git a/chapter06/adjustingtoolchain.xml b/chapter06/adjustingtoolchain.xml
index fd5ba1676..522727785 100644
--- a/chapter06/adjustingtoolchain.xml
+++ b/chapter06/adjustingtoolchain.xml
@@ -43,5 +43,33 @@ is unavoidable, but luckily does not present a problem. There are no
 libraries in that location as all the temporary tools libraries are
 located in <filename class="directory">/tools/lib</filename>.</para>
 
+<caution><para>It is imperative at this point to stop and ensure that the
+basic functionality of the adjusted toolchain is working as expected. We are
+going to perform a simple sanity check:</para>
+
+<para><screen><userinput>echo 'main(){}' > dummy.c
+gcc dummy.c
+readelf -l a.out | grep ': /lib'</userinput></screen></para>
+
+<para>If everything is working correctly, the output of the last command will
+be:</para>
+
+<para><screen>[Requesting program interpreter: /lib/ld-linux.so.2]
+</screen></para>
+
+<para>If you did not receive the output as shown above then something is
+seriously wrong. You will need to investigate and retrace your steps to find
+out where the problem is and correct it. There is no point in continuing
+until this is done. Most likely, something went wrong with the specs file
+amendment above. Note especially that <filename>/lib</filename> now appears as
+the prefix of our dynamic linker. Of course, if you are working on a platform
+where the name of the dynamic linker is something other than <filename>
+ld-linux.so.2</filename> then the output will be slightly different.</para>
+
+<para>Once you are satisfied that all is well, clean up the test files:</para>
+
+<para><screen><userinput>rm dummy.c a.out</userinput></screen></para>
+</caution>
+
 </sect1>
 
diff --git a/chapter06/binutils-inst.xml b/chapter06/binutils-inst.xml
index d55f9b49a..c414e52a4 100644
--- a/chapter06/binutils-inst.xml
+++ b/chapter06/binutils-inst.xml
@@ -2,6 +2,10 @@
 
 <sect2><title>Installation of Binutils</title>
 
+<note><para>The testsuite for Binutils in this chapter is considered
+<emphasis>critical</emphasis>. Do not skip it under any circumstances.</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
diff --git a/chapter06/gcc-inst.xml b/chapter06/gcc-inst.xml
index 5e5dab528..21e22c55c 100644
--- a/chapter06/gcc-inst.xml
+++ b/chapter06/gcc-inst.xml
@@ -3,6 +3,9 @@
 <sect2>
 <title>Installation of GCC</title>
 
+<note><para>The testsuite for GCC in this chapter is considered <emphasis>
+critical</emphasis>. Do not skip it under any circumstances.</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
diff --git a/chapter06/glibc-inst.xml b/chapter06/glibc-inst.xml
index 376bbdacf..099dc4dc9 100644
--- a/chapter06/glibc-inst.xml
+++ b/chapter06/glibc-inst.xml
@@ -9,6 +9,9 @@ pointing at <filename>/tools</filename>. We cannot adjust the specs and
 ldscripts before the Glibc install, because the Glibc autoconf tests would then
 give bogus results and thus defeat our goal of achieving a clean build.</para>
 
+<note><para>The testsuite for Glibc in this chapter is considered <emphasis>
+critical</emphasis>. Do not skip it under any circumstances.</para></note>
+
 <para>Before starting to build Glibc, remember to unpack the Glibc-linuxthreads
 again inside the <filename>glibc-&glibc-version;</filename> directory, and to
 unset any environment variables that override the default optimization