Index: chapter04/aboutsbus.xml
===================================================================
--- chapter04/aboutsbus.xml (revision b99b7d3a6e77c4728dcf9903f71f2e3fdd95daca)
+++ chapter04/aboutsbus.xml (revision ee714d385e3f3b943e3fa4407847cfdeb8a435f7)
@@ -21,5 +21,5 @@
The SBU measure works as follows. The first package to be compiled
- from this book is Binutils in . The
+ from this book is binutils in . The
time it takes to compile this package is what will be referred to as the
Standard Build Unit or SBU. All other compile times will be expressed relative
@@ -28,7 +28,7 @@
For example, consider a package whose compilation time is 4.5
SBUs. This means that if a system took 10 minutes to compile and
- install the first pass of Binutils, it will take
+ install the first pass of binutils, it will take
approximately 45 minutes to build this example package.
- Fortunately, most build times are shorter than the one for Binutils.
+ Fortunately, most build times are shorter than the one for binutils.
In general, SBUs are not entirely accurate because they depend on many
@@ -42,11 +42,11 @@
make" by either setting an environment variable or telling the
make program how many processors are available. For
- instance, a Core2Duo can support two simultaneous processes with:
+ instance, an Intel i5-6500 COU can support four simultaneous processes with:
- export MAKEFLAGS='-j 2'
+ export MAKEFLAGS='-j4'
or just building with:
- make -j2
+ make -j4
When multiple processors are used in this way, the SBU units in the
Index: chapter04/abouttestsuites.xml
===================================================================
--- chapter04/abouttestsuites.xml (revision b99b7d3a6e77c4728dcf9903f71f2e3fdd95daca)
+++ chapter04/abouttestsuites.xml (revision ee714d385e3f3b943e3fa4407847cfdeb8a435f7)
@@ -19,17 +19,18 @@
Some test suites are more important than others. For example,
- the test 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. The test suites for GCC and Glibc can
+ the test 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. The test suites for GCC and glibc can
take a very long time to complete, especially on slower hardware, but
are strongly recommended.
- Running the test suites in
+ Running the test suites in
+ and
is impossible, since the programs are compiled with a cross-compiler,
so are not supposed to be able to run on the build host.
- A common issue with running the test suites for Binutils and GCC
+ A common issue with running the test suites for binutils and GCC
is running out of pseudo terminals (PTYs). This can result in a high
number of failing tests. This may happen for several reasons, but the
Index: chapter04/addinguser.xml
===================================================================
--- chapter04/addinguser.xml (revision b99b7d3a6e77c4728dcf9903f71f2e3fdd95daca)
+++ chapter04/addinguser.xml (revision ee714d385e3f3b943e3fa4407847cfdeb8a435f7)
@@ -12,6 +12,6 @@
When logged in as user root,
- making a single mistake can damage or destroy a system. Therefore, we
- recommend building the packages in the next chapter as an unprivileged user.
+ making a single mistake can damage or destroy a system. Therefore,
+ the packages in the next two chapters are built as an unprivileged user.
You could use your own user name, but to make it easier to set up a clean
working environment, create a new user called lfs
- This is the actual name for the created group and user.
+ This is the actual name for the created user.
@@ -96,5 +96,5 @@
Next, login as user lfs.
This can be done via a virtual console, through a display manager, or with
- the following substitute user command:
+ the following substitute/switch user command:
su - lfs
Index: chapter04/settingenviron.xml
===================================================================
--- chapter04/settingenviron.xml (revision b99b7d3a6e77c4728dcf9903f71f2e3fdd95daca)
+++ chapter04/settingenviron.xml (revision ee714d385e3f3b943e3fa4407847cfdeb8a435f7)
@@ -51,5 +51,5 @@
- The meaning of the command line options in .bashrc
+ The meaning of the settings in .bashrc
@@ -137,5 +137,5 @@
By putting $LFS/tools/bin ahead of the
standard PATH, the cross-compiler installed at the beginning
- of is picked up by the shell
+ of is picked up by the shell
immediately after its installation. This, combined with turning off hashing,
limits the risk that the compiler from the host be used instead of the
@@ -148,5 +148,5 @@
While the above commands have set some variables, in order
- to make them visible within any sub-shells, we export them
+ to make them visible within any sub-shells, we export them.