minor textual changes to chapter 5

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

chapter05/bash-inst.xml

@@ -15,7 +15,7 @@ development package. This package is often called something like
 this package is already installed, or you just installed it, check for the
 two files again. Often the <filename>libcurses.a</filename> file is (still)
 missing. If so, create <filename>libcurses.a</filename> as a symlink
-by running the following commands as user <emphasis>root:</emphasis></para>
+by running the following command as user <emphasis>root:</emphasis></para>
 
 <para><screen><userinput>ln -s libncurses.a /usr/lib/libcurses.a</userinput></screen></para>
 
@@ -50,7 +50,7 @@ being just fine because we will reinstall Bash in Chapter 6 anyway,
 where we will use libncurses), but it's a good test to make sure that
 the Ncurses package has been installed properly. If not, you will get in
 trouble later on in this chapter when you install the Texinfo package.
-That package requires ncurses, and termcap can't reliably be used
+That package requires ncurses, and termcap can't be used
 there.</para></listitem>
 </itemizedlist>
 

chapter05/binutils-inst.xml

@@ -7,8 +7,7 @@
 optimization flags (including the -march and -mcpu options). Binutils is
 best left alone. 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. You have been
+recommend unsetting or modifying them when building binutils.</para>
-warned.</para>
 
 <para>It is recommended by the Binutils installation documentation to build
 Binutils outside of the source directory in a dedicated directory:</para>

chapter05/diffutils-inst.xml

@@ -13,11 +13,12 @@
 <itemizedlist>
 <listitem><para><userinput>LDFLAGS="-static":</userinput> This is the most
 common way to tell a package that all programs should be statically linked.
-This way the <emphasis>LDFLAGS</emphasis> environment variable is set but
+This way the <emphasis>LDFLAGS</emphasis> environment variable is set, but
 only in the subshell that the <filename>configure</filename> script runs
 in. When <userinput>configure</userinput> has done its job, the
-<emphasis>LDFLAGS</emphasis> variable won't exist
+<emphasis>LDFLAGS</emphasis> environment variable won't exist anymore
-anymore.</para></listitem>
+and the <filename>Makefile</filename> files contain will contain this
+variable locally.</para></listitem>
 
 <listitem><para><userinput>CPPFLAGS=-Dre_max_failures=re_max_failures2:</userinput>
 The <emphasis>CPPFLAGS</emphasis> variable is a variable that's read by the

chapter05/fileutils-inst.xml

@@ -15,13 +15,13 @@ able to compile this package at all, even when your system has an AMD CPU
 and has Glibc-2.2.3 (or higher) installed. If that's the case, you'll need
 to remove the fileutils-&fileutils-version; directory and unpack it again
 from the tarball before continuing. We believe this may be the case when
-your distribution has altered Glibc-2.2.3 somehow, but details are
+your distribution has altered Glibc-2.2.3 somehow, but the exact details
-unavailable at this time.</para>
+are unknown.</para>
 
 <para>To fix this package to compile properly on AMD/Glibc-2.2.3
 machines, run the following command. Do <emphasis>NOT</emphasis>
 attempt this fix if you don't have Glibc-2.2.3 installed. It will more 
-than likely result in all kinds of compile time problems.</para>
+than likely result in all kinds of compilation problems.</para>
 
 <para><screen><userinput>patch -Np1 -i ../fileutils-&fileutils-patch-version;.patch</userinput></screen></para>
 

chapter05/gcc-inst.xml

@@ -10,8 +10,7 @@ the gcc-core tarball needs to be unpacked at this time.</para>
 default optimization flags (including the -march and -mcpu options). GCC is
 best left alone. 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 GCC. You have
+recommend unsetting or modifying them when building GCC.</para>
-been warned.</para>
 
 <para>It is recommended by the GCC installation documentation to build
 GCC outside of the source directory in a dedicated directory:</para>
@@ -32,7 +31,8 @@ cd ../gcc-build</userinput></screen></para>
 <listitem><para><userinput>--prefix=/static:</userinput> This is NOT a
 typo. GCC hard codes some paths while compiling and so we need to pass
 <filename class="directory">/static</filename> as the prefix during the
-configure stage. We pass the real install prefix during the installation
+configure stage. We will pass the real installation prefix (<filename
+class="directory">$LFS/static</filename> during the installation
 stage later on.</para></listitem>
 
 <listitem><para><userinput>--disable-shared:</userinput> This prevents the
@@ -82,7 +82,7 @@ If so, it will fix them and put them in
 <filename>$LFS/static/lib/gcc-lib/i686-pc-linux-gnu/3.2</filename>. Later on
 in chapter 6 you will install Glibc which will put its header files in
 <filename>/usr/include</filename>. Next you will install other programs that
-use the Glibc headers. GCC will look in
+use the Glibc headers and GCC will look in
 <filename>/static/lib/gcc-lib</filename> before looking in
 <filename>/usr/include</filename>, with the result of finding and using the
 fixed Glibc header files from your host distribution, which are probably

chapter05/shellutils-inst.xml

@@ -31,8 +31,7 @@ NOTE: to install su, run 'make install-root' as root</screen></blockquote>
 <para>You can safely ignore that warning. You need to be logged in as root
 in order to install su the way Sh-utils wants to install it, which is being
 suid root. Because we don't need su during Chapter 6, and su will be properly
-installed when we re-install Sh-utils in Chapter 6, you can just
+installed when we re-install Sh-utils in Chapter 6.</para>
-pretend you didn't see it.</para>
 
 </sect2>
 

index.xml

@@ -5,7 +5,7 @@
 <!ENTITY book SYSTEM "book/book.xml">
 
 <!ENTITY version "20030122">
-<!ENTITY releasedate "January 22nd, 2003">
+<!ENTITY releasedate "January 27nd, 2003">
 
 <!ENTITY ftp-root "ftp://ftp.linuxfromscratch.org">
 <!ENTITY http-root "http://ftp.linuxfromscratch.org">