aboutsummaryrefslogtreecommitdiffstats
path: root/chapter05
diff options
context:
space:
mode:
authorGerard Beekmans <gerard@linuxfromscratch.org>2002-04-19 18:27:01 +0000
committerGerard Beekmans <gerard@linuxfromscratch.org>2002-04-19 18:27:01 +0000
commite69a59f2e44d780a6ca26e71b96ab86e58b0fe58 (patch)
treedcb4085cb3e4a2cf232de00b2e95a7a6f639a3c3 /chapter05
parent747f5dda8e125740a8f732e784903f017a84f80b (diff)
various fixes
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@1840 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Diffstat (limited to 'chapter05')
-rw-r--r--chapter05/binutils-exp.xml2
-rw-r--r--chapter05/binutils-inst.xml9
-rw-r--r--chapter05/fileutils-inst.xml6
-rw-r--r--chapter05/gcc-inst.xml11
-rw-r--r--chapter05/kernel.xml2
5 files changed, 16 insertions, 14 deletions
diff --git a/chapter05/binutils-exp.xml b/chapter05/binutils-exp.xml
index 6722b5dda..1f631d55f 100644
--- a/chapter05/binutils-exp.xml
+++ b/chapter05/binutils-exp.xml
@@ -2,7 +2,7 @@
<title>Command explanations</title>
<para><userinput>mkdir ../binutils-build:</userinput> The installation
-instructions for Binutils recommend creating a seperate build directory
+instructions for Binutils recommend creating a separate build directory
instead of compiling the package inside the source tree. So, we create a
binutils-build directory and work from there.</para>
diff --git a/chapter05/binutils-inst.xml b/chapter05/binutils-inst.xml
index a64e6b687..55beb8d9f 100644
--- a/chapter05/binutils-inst.xml
+++ b/chapter05/binutils-inst.xml
@@ -2,10 +2,11 @@
<title>Installation of Binutils</title>
<para>This package is known to behave badly when you have changed its default
-optimization flags (including the -march and -mcpu options). Binutils is
-best left alone, so we recommend you unsetting CFLAGS, CXXFLAGS and other
-such variables/settings that would change the default optimization that
-it comes with.</para>
+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
+warned.</para>
<para>Install Binutils by running the following commands:</para>
diff --git a/chapter05/fileutils-inst.xml b/chapter05/fileutils-inst.xml
index 9bd395ac6..6d630b2c7 100644
--- a/chapter05/fileutils-inst.xml
+++ b/chapter05/fileutils-inst.xml
@@ -1,7 +1,7 @@
<sect2>
<title>Installation of Fileutils</title>
-<para>The programs from a statically linked fileutils package may cause
+<para>The programs from a statically linked Fileutils package may cause
segmentation faults on certain systems, if your distribution has
Glibc-2.2.3 or higher installed. It also seems to happen mostly on machines
powered by an AMD CPU, but there is a case or two where an Intel system
@@ -26,7 +26,7 @@ sed -e 's/\(.*\)\(fopen-safer\.c \)\\/\1\2atexit.c \\/' \
&nbsp;&nbsp;&nbsp;-e 's/\(.*\)\(idcache\$U\.\$.*\)\\/\1\2atexit$U.$(OBJEXT) \\/' \
&nbsp;&nbsp;&nbsp;lib/Makefile.in.backup &gt; lib/Makefile.in</userinput></screen></para>
-<para>Install fileutils by running the following commands:</para>
+<para>Install Fileutils by running the following commands:</para>
<para><screen><userinput>./configure --disable-nls \
&nbsp;&nbsp;&nbsp;--prefix=$LFS/usr --bindir=$LFS/bin &amp;&amp;
@@ -35,7 +35,7 @@ make install &amp;&amp;
cd $LFS/usr/bin &amp;&amp;
ln -sf ../../bin/install</userinput></screen></para>
-<para>Once you have installed fileutils, you can test whether the
+<para>Once you have installed Fileutils, you can test whether the
segmentation fault problem has been avoided by running
<userinput>$LFS/bin/ls</userinput>. If this works, then you are OK. If
not, then you need to re-do the installation using the sed commands if
diff --git a/chapter05/gcc-inst.xml b/chapter05/gcc-inst.xml
index ca7244637..3b52c7dc5 100644
--- a/chapter05/gcc-inst.xml
+++ b/chapter05/gcc-inst.xml
@@ -1,11 +1,12 @@
<sect2>
<title>Installation of GCC</title>
-<para>This package is known to behave badly when you have changed its default
-optimization flags (including the -march and -mcpu options). GCC is best
-left alone, so we recommend you unsetting CFLAGS, CXXFLAGS and other
-such variables/settings that would change the default optimization that
-it comes with.</para>
+<para>This package is known to behave badly when you have changed its
+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 binutils. You have
+been warned.</para>
<para>Install GCC by running the following commands:</para>
diff --git a/chapter05/kernel.xml b/chapter05/kernel.xml
index 2d1168fac..07839f118 100644
--- a/chapter05/kernel.xml
+++ b/chapter05/kernel.xml
@@ -1,5 +1,5 @@
<sect1 id="ch05-kernel">
-<title>Installing Linux Kernel-&kernel-version;</title>
+<title>Installing Linux-&kernel-version;</title>
<?dbhtml filename="kernel.html" dir="chapter05"?>
<screen>Estimated build time: &kernel-time-static;