Minor textual shuffles.

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

1 files changed, 28 insertions, 28 deletions

diff --git a/chapter05/binutils-pass1.xml b/chapter05/binutils-pass1.xml
index 25cc593f4..13eac6710 100644
--- a/chapter05/binutils-pass1.xml
+++ b/chapter05/binutils-pass1.xml
@@ -17,11 +17,11 @@
 because both Glibc and GCC perform various tests on the available linker and
 assembler to determine which of their own features to enable.</para>
 
-<para>This package is known to behave badly when you have changed its default
-optimization flags (including the -march and -mcpu options). Therefore, if
-you have defined any environment variables that override default
-optimizations, such as CFLAGS and CXXFLAGS, we recommend unsetting or
-modifying them when building Binutils.</para>
+<para>This package is known to behave badly when you change its default
+optimization flags (including the <emphasis>-march</emphasis> and
+<emphasis>-mcpu</emphasis> options). Therefore, if you have defined any
+environment variables that override default optimizations, such as CFLAGS and
+CXXFLAGS, we recommend unsetting them when building Binutils.</para>
 
 <para>The Binutils documentation recommends building Binutils outside of the
 source directory in a dedicated build directory:</para>
@@ -30,9 +30,11 @@ source directory in a dedicated build directory:</para>
 cd ../binutils-build</userinput></screen>
 
 <note><para>If you want the SBU values listed in the rest of the book to be of
-any use, you will have to measure the time it takes to build this package. To
-achieve this easily, you could do something like:
-<userinput>time { ./configure ... &amp;&amp; ... &amp;&amp; ... &amp;&amp; make install; }</userinput>.</para></note>
+any use, you will have to measure the time it takes to build this package --
+from the configuration upto and including the first install. To achieve this
+easily, you could wrap the four commands in a <command>time</command> command
+like this: <userinput>time { ./configure ... &amp;&amp; ... &amp;&amp; ...
+&amp;&amp; make install; }</userinput>.</para></note>
 
 <para>Now prepare Binutils for compilation:</para>
 
@@ -66,18 +68,16 @@ problem.</para></listitem>
 
 <listitem><para><userinput>LDFLAGS="-all-static"</userinput>: This tells the
 linker that all the Binutils programs should be linked statically. However,
-strictly speaking, <emphasis>"-all-static"</emphasis> is first passed to the
-<command>libtool</command> program which then passes
-<emphasis>"-static"</emphasis> on to the linker.</para></listitem>
+strictly speaking, <emphasis>"-all-static"</emphasis> is passed to the
+<command>libtool</command> program, which then passes
+<emphasis>"-static"</emphasis> to the linker.</para></listitem>
 </itemizedlist>
 
-<para>Compilation is now complete. This is the point where we would normally
-run the test suite. But as discussed earlier, we don't recommend running the
-test suites for the temporary tools here in this chapter. However, even if we
-still wanted to run the Binutils test suite, we're unable do so at this early
-stage because the test suite framework is not yet in place. Not only that, the
-programs from this first pass will soon be overwritten by those installed in
-the second pass.</para>
+<para>Compilation is complete. Normally we would now run the test suite, but
+at this early stage the test suite framework (Tcl, Expect and DejaGnu) is not
+yet in place. And there would be little point in running the tests anyhow,
+since the programs from this first pass will soon be replaced by those from the
+second.</para>
 
 <para>And install the package:</para>
 
@@ -92,16 +92,16 @@ make -C ld LDFLAGS="-all-static" LIB_PATH=/tools/lib</userinput></screen>
 
 <itemizedlist>
 <listitem><para><userinput>-C ld clean</userinput>: This tells the make program
-to remove all the compiled files, but only in the <filename>ld</filename>
-subdirectory.</para></listitem>
-
-<listitem><para><userinput>-C ld LDFLAGS="-all-static" LIB_PATH=/tools/lib</userinput>:
-This option rebuilds everything in the <filename>ld</filename> subdirectory.
-Specifying the LIB_PATH makefile variable on the command line allows us to
-override the default value and have it point to our temporary tools location.
-The value of this variable specifies the linker's default library search path.
-You'll see how this preparation is used later on in the
-chapter.</para></listitem>
+to remove all the compiled files in the <filename
+class="directory">ld</filename> subdirectory.</para></listitem>
+
+<listitem><para><userinput>-C ld LDFLAGS="-all-static"
+LIB_PATH=/tools/lib</userinput>: This option rebuilds everything in the
+<filename class="directory">ld</filename> subdirectory. Specifying the LIB_PATH
+makefile variable on the command line allows us to override the default value
+and have it point to our temporary tools location. The value of this variable
+specifies the linker's default library search path. You will see how this
+preparation is used later on in the chapter.</para></listitem>
 </itemizedlist>
 
 <!-- HACK - Force some whitespace to appease tidy -->