From 15b6ed42732e28bdc509ecf0ab9ed9c14915d153 Mon Sep 17 00:00:00 2001 From: Alex Gronenwoud Date: Wed, 21 Jan 2004 22:15:22 +0000 Subject: Adding a few cross references. git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@3180 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689 --- chapter02/aboutsbus.xml | 6 +++--- chapter02/abouttestsuites.xml | 42 +++++++++++++++++++++--------------------- 2 files changed, 24 insertions(+), 24 deletions(-) (limited to 'chapter02') diff --git a/chapter02/aboutsbus.xml b/chapter02/aboutsbus.xml index 2925f8a74..6d0cc1a56 100644 --- a/chapter02/aboutsbus.xml +++ b/chapter02/aboutsbus.xml @@ -12,9 +12,9 @@ with the idea of using the Static Binutils Unit (abbreviated to SBU). 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. +statically linked Binutils in, 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. For example, the time it takes to build the static version of GCC is &gcc-time-tools-pass1;s. This means that if on your system it took 10 minutes diff --git a/chapter02/abouttestsuites.xml b/chapter02/abouttestsuites.xml index 1403629c3..8b4665960 100644 --- a/chapter02/abouttestsuites.xml +++ b/chapter02/abouttestsuites.xml @@ -3,9 +3,9 @@ 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. @@ -13,29 +13,29 @@ free. 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 period of time to complete, especially on slower -hardware. +can take a very long time to complete, especially on slower hardware. 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. +the test suites in . 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 are temporary and eventually discarded. For the +average reader of this book we recommend not to run the +test suites in . 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. -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. +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. 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 devpts file -system set up correctly. We'll discuss this in more detail later on in Chapter -5. +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 +devpts file system set up correctly. We'll discuss this in +more detail later on in . -- cgit v1.2.3-54-g00ecf