Changeset 15b6ed4 for chapter02

Timestamp:

01/21/2004 10:15:22 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:

5618bb7

Parents:

d12fdb1

Message:

Adding a few cross references.

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

Location:

chapter02

Files:

• aboutsbus.xml (modified) (1 diff)
• abouttestsuites.xml (modified) (2 diffs)

chapter02/aboutsbus.xml

@@ -13 +13 @@
 
 <para>It works like this: the first package you compile in this book is the
-statically linked Binutils in Chapter 5, and the time it takes to compile this
-package is what we call the "Static Binutils Unit" or "SBU". All other compile
-times will be expressed relative to this time.</para>
+statically linked Binutils in<xref linkend="chapter05"/>, and the time it
+takes to compile this package is what we call the "Static Binutils Unit" or
+"SBU". All other compile times will be expressed relative to this time.</para>
 
 <para>For example, the time it takes to build the static version of GCC is

chapter02/abouttestsuites.xml

@@ -4 +4 @@
 
 <para>Most packages provide a test suite. Running the test suite for a newly
-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
+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>
@@ -14 +14 @@
 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 period of time to complete, especially on slower
-hardware.</para>
+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 Chapter 5. There can be no escaping the fact that the host
-system always exerts influence on the Chapter 5 tests, often causing weird and
-inexplicable failures. Not only that, the tools built in Chapter 5 are
-temporary and eventually discarded. For the average reader of this book we
-recommend not to run the Chapter 5 test suites. The instructions for running
-the Chapter 5 test suites are still provided for the benefit of testers and
-developers but they are strictly optional for everyone else.</para>
+the test suites in <xref linkend="chapter05"/>. 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="chapter05"/> 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="chapter05"/>. 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>
 
-<para>As you progress through the book and encounter the build 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 it or not.</para>
+<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>
 
 <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 any 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 Chapter
-5.</para></note>
+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="chapter05"/>.</para></note>
 
 </sect1>