aboutsummaryrefslogtreecommitdiffstats
path: root/chapter04/aboutsbus.xml
diff options
context:
space:
mode:
authorDavid Bryant <davidbryant@gvtc.com>2022-09-27 13:42:07 -0500
committerDavid Bryant <davidbryant@gvtc.com>2022-09-27 13:42:07 -0500
commitef93b660064eed234161eb75619ebb36618d86ee (patch)
treee28608536e26c320f9e5983a68dfb3e5fcf48a87 /chapter04/aboutsbus.xml
parentec7b0466231b31f33fec76358d71fc06ff399a63 (diff)
Adjust English idiom and clarify directions (chapters 4.5 and 4.6).
Diffstat (limited to 'chapter04/aboutsbus.xml')
-rw-r--r--chapter04/aboutsbus.xml24
1 files changed, 12 insertions, 12 deletions
diff --git a/chapter04/aboutsbus.xml b/chapter04/aboutsbus.xml
index 1928423ea..82934d851 100644
--- a/chapter04/aboutsbus.xml
+++ b/chapter04/aboutsbus.xml
@@ -13,25 +13,25 @@
<para>Many people would like to know beforehand approximately how long
it takes to compile and install each package. Because Linux From
Scratch can be built on many different systems, it is impossible to
- provide accurate time estimates. The biggest package (Glibc) will
+ provide absolute time estimates. The biggest package (Glibc) will
take approximately 20 minutes on the fastest systems, but could take
up to three days on slower systems! Instead of providing actual times,
the Standard Build Unit (SBU) measure will be
used instead.</para>
<para>The SBU measure works as follows. The first package to be compiled
- from this book is binutils in <xref linkend="chapter-cross-tools"/>. 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
- to this time.</para>
+ is binutils in <xref linkend="chapter-cross-tools"/>. The
+ time it takes to compile this package is what we will refer to as the
+ Standard Build Unit or SBU. All other compile times will be expressed in
+ terms of this unit of time.</para>
<para>For example, consider a package whose compilation time is 4.5
- SBUs. This means that if a system took 10 minutes to compile and
+ SBUs. This means that if your system took 10 minutes to compile and
install the first pass of binutils, it will take
- <emphasis>approximately</emphasis> 45 minutes to build this example package.
- Fortunately, most build times are shorter than the one for binutils.</para>
+ <emphasis>approximately</emphasis> 45 minutes to build the example package.
+ Fortunately, most build times are shorter than one SBU.</para>
- <para>In general, SBUs are not entirely accurate because they depend on many
+ <para>SBUs are not entirely accurate because they depend on many
factors, including the host system's version of GCC. They are provided here
to give an estimate of how long it might take to install a package, but the
numbers can vary by as much as dozens of minutes in some cases.</para>
@@ -45,15 +45,15 @@
<screen role="nodump"><userinput>export MAKEFLAGS='-j4'</userinput></screen>
- <para>or just building with:</para>
+ <para>or by building with:</para>
<screen role="nodump"><userinput>make -j4</userinput></screen>
<para>When multiple processors are used in this way, the SBU units in the
book will vary even more than they normally would. In some cases, the make
step will simply fail. Analyzing the output of the build process will also
- be more difficult because the lines of different processes will be
- interleaved. If you run into a problem with a build step, revert back to a
+ be more difficult because the lines from different processes will be
+ interleaved. If you run into a problem with a build step, revert to a
single processor build to properly analyze the error messages.</para>
</note>