Changeset c91dd5b for chapter02

Timestamp:

02/11/2004 10:02:10 PM (20 years ago)

Author:

Alex Gronenwoud <alex@…>

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:

a0b689e

Parents:

5cd6caa

Message:

Making the test suites in chapter 5 more clearly optional.

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

File:

• chapter02/abouttestsuites.xml (modified) (1 diff)

chapter02/abouttestsuites.xml

@@ -6 +6 @@
 built package is generally a good idea, as it can provide a nice sanity check
 that everything compiled correctly. A test suite that passes its set of checks
-usually proves that the package is functioning mostly as the developer
-intended. It does not, however, guarantee that the package is totally bug
-free.</para>
+usually proves that the package is functioning as the developer intended. It
+does not, however, guarantee that the package is totally bug free.</para>
 
 <para>Some test suites are more important than others. For example, the test
-suites for the core toolchain packages -- GCC, Binutils, and Glibc (the C
-library) -- are of the utmost importance due to their central role in a
-properly functioning system. But be warned, the test suites for GCC and Glibc
-can take a very long time to complete, especially on slower hardware.</para>
+suites for the core toolchain packages -- GCC, Binutils, and Glibc -- are of
+the utmost importance due to their central role in a properly functioning
+system. But be warned, the test suites for GCC and Glibc can take a very long
+time to complete, especially on slower hardware.</para>
 
-<para>Experience has shown us that there is little to be gained from running
-the test suites in <xref linkend="chapter-temporary-tools"/>. There can be no escaping the
-fact that the host system always exerts influence on the tests in that chapter,
-often causing weird and inexplicable failures. Not only that, the tools built
-in <xref linkend="chapter-temporary-tools"/> are temporary and eventually discarded. For the
-average reader of this book we recommend <emphasis>not</emphasis> to run the
-test suites in <xref linkend="chapter-temporary-tools"/>. The instructions for running those
-test suites are still provided for the benefit of testers and developers, but
-they are strictly optional for everyone else.</para>
+<note><para>Experience has shown us that there is little to be gained from running
+the test suites in <xref linkend="chapter-temporary-tools"/>. There can be no
+escaping the fact that the host system always exerts some influence on the
+tests in that chapter, often causing weird and inexplicable failures. Not only
+that, the tools built in <xref linkend="chapter-temporary-tools"/> are
+temporary and eventually discarded. For the average reader of this book we
+recommend <emphasis>not</emphasis> to run the test suites in <xref
+linkend="chapter-temporary-tools"/>. The instructions for running those test
+suites are still provided for the benefit of testers and developers, but they
+are strictly optional for everyone else.</para></note>
 
-<para>As you progress through the book and encounter the commands to run the
-various test suites, we'll guide you on the relative importance of the test
-suite in question, so that you can decide for yourself whether to run that one
-or not.</para>
+<para>A common problem when running the test suites for Binutils and GCC is
+running out of pseudo terminals (PTYs for short). The symptom is a very high
+number of failing tests. This can happen for several reasons, but the most
+likely cause is that the host system doesn't have the
+<emphasis>devpts</emphasis> file system set up correctly. We'll discuss this in
+more detail later on in <xref linkend="chapter-temporary-tools"/>.</para>
 
-<note><para>A common problem when running the test suites for Binutils and GCC
-is running out of pseudo terminals (PTYs for short). The symptom is an
-unusually high number of failing tests. This can happen for a number of
-reasons. Most likely is that the host system doesn't have the
-<emphasis>devpts</emphasis> file system set up correctly. We'll discuss this in
-more detail later on in <xref linkend="chapter-temporary-tools"/>.</para></note>
+<para>Sometimes package test suites will give false failures. You can
+consult the LFS Wiki at <ulink url="&wiki-root;"/> to verify that these
+failures are normal. This applies to all tests throughout the book.</para>
 
 </sect1>