Changeset 1f53626 for chapter05

Timestamp:

09/16/2003 07:28:26 AM (21 years ago)

Author:

Greg Schafer <greg@…>

Branches:

10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 12.2, 12.2-rc1, 6.0, 6.1, 6.1.1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, v5_0, v5_1, v5_1_1, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/loongarch-12.2, xry111/mips64el, xry111/multilib, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc

Children:

2260572

Parents:

18b65e2b

Message:

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

Location:

chapter05

Files:

• binutils-pass1-inst.xml (modified) (1 diff)
• binutils-pass2-inst.xml (modified) (1 diff)
• gcc-pass1-inst.xml (modified) (1 diff)
• gcc-pass2-inst.xml (modified) (1 diff)
• glibc-inst.xml (modified) (1 diff)
• lockingglibc.xml (modified) (1 diff)

chapter05/binutils-pass1-inst.xml

@@ -7 +7 @@
 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 testsuite at this early stage. Firstly, the testsuite
+framework is not yet in place and secondly, 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

chapter05/binutils-pass2-inst.xml

@@ -3 +3 @@
 <sect2>
 <title>Re-installation of Binutils</title>
+
+<note><para>It's worth noting that the Binutils testsuite we run in this
+chapter is considered not as critical as the one we run in Chapter 6.</para>
+</note>
 
 <para>First create a separate build directory again:</para>

chapter05/gcc-pass1-inst.xml

@@ -6 +6 @@
 <para>Unpack only the GCC-core tarball, as we won't be needing a C++ compiler
 for the moment.</para>
+
+<note><para>Even though GCC is an important toolchain package, we are not
+going to run the testsuite at this early stage. Firstly, the testsuite 
+framework is not yet in place and secondly, 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

chapter05/gcc-pass2-inst.xml

@@ -11 +11 @@
 which does not properly support the devpts filesystem will cause most of
 these tests to fail.</para>
+
+<note><para>It's worth noting that the GCC testsuite we run in this chapter is
+considered not as critical as the one we run in Chapter 6.</para></note>
 
 <para>Unpack all three GCC tarballs in one and the same working directory.

chapter05/glibc-inst.xml

@@ -8 +8 @@
 Glibc-linuxthreads in that directory, not in <filename>/usr/src</filename> as
 you would normally do.</para>
+
+<note><para>We are going to run the testsuite for Glibc in this chapter.
+However, it's worth noting that the Glibc testsuite we run in this chapter is
+considered not as critical as the one we run in Chapter 6.</para></note>
 
 <para>This package is known to behave badly when you have changed its

chapter05/lockingglibc.xml

@@ -46 +46 @@
 <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>