Changeset 443cace for chapter05/gcc-pass2.xml

Timestamp:

01/17/2004 01:37:37 AM (20 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, 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_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/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc

Children:

51fe215

Parents:

b05a831

Message:

Implemented changes to make the running of the Chapter 5 test
suites strictly optional i.e. the default action for the
average reader is to not run them. Closes 719.

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

File:

• chapter05/gcc-pass2.xml (modified) (2 diffs)

chapter05/gcc-pass2.xml

@@ -16 +16 @@
 <para>The tools required to test GCC and Binutils are installed now (Tcl, Expect
 and DejaGnu). We can continue on rebuilding GCC and Binutils, link them against
-the new Glibc, and test them properly. One thing to note, however, is that these
-test suites are highly dependent on properly functioning pseudo terminals (PTYs)
-which are provided by your host distribution. These days, PTYs are most commonly
-implemented via the <emphasis>devpts</emphasis> file system. You can quickly
-check if your host system is set up correctly in this regard by performing a
-simple test:</para>
+the new Glibc, and test them properly (if performing the test suites in this
+chapter). One thing to note, however, is that these test suites are highly
+dependent on properly functioning pseudo terminals (PTYs) which are provided by
+your host distribution. These days, PTYs are most commonly implemented via the
+<emphasis>devpts</emphasis> file system. You can quickly check if your host
+system is set up correctly in this regard by performing a simple test:</para>
 
 <screen><userinput>expect -c "spawn ls"</userinput></screen>
@@ -117 +117 @@
 version of the GCC sources we used earlier.</para>
 
-<note><para>It's worth pointing out that running the GCC test suite here
-is considered not as important as running it in
-<xref linkend="chapter06"/>.</para></note>
-
-<para>Test the results:</para>
+<para>Compilation is now complete. As discussed earlier, we don't recommend
+running the test suites for the temporary tools here in this chapter. If you
+still want to run the GCC test suite anyway, the following command will do
+so:</para>
 
 <screen><userinput>make -k check</userinput></screen>