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

1 files changed, 29 insertions, 0 deletions

diff --git a/chapter05/lockingglibc.xml b/chapter05/lockingglibc.xml
index bd15b4a7f..285de303c 100644
--- a/chapter05/lockingglibc.xml
+++ b/chapter05/lockingglibc.xml
@@ -45,6 +45,35 @@ following commands to eliminate this possibility.</para>
 
 <para><screen><userinput>rm -f /tools/lib/gcc-lib/*/*/include/{pthread.h,bits/sigthread.h}</userinput></screen></para>
 
+<caution><para>It is imperative at this point to stop and ensure that the
+basic functionality of the new 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 ': /tools'</userinput></screen></para>
+
+<para>If everything is working correctly, the output of the last command will
+be:</para>
+
+<para><screen>[Requesting program interpreter: /tools/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>/tools/lib</filename> 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>
+
 <para>This completes the installation of the self-contained toolchain, which
 can now be used to build the rest of the temporary tools.</para>