diff options
| author | Timothy Bauscher <timothy@linuxfromscratch.org> | 2002-09-24 04:52:43 +0000 |
|---|---|---|
| committer | Timothy Bauscher <timothy@linuxfromscratch.org> | 2002-09-24 04:52:43 +0000 |
| commit | 695ae0bc31b390e1a544b0bd2f613ed514731168 (patch) | |
| tree | 325d247284a14ec2f45f24150665fdb9db4271ed /chapter05 | |
| parent | 4a7171007fe7374ca39694ade3b062d18a496caa (diff) | |
Applied Bill's chapter 5 fixes patch.
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2133 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Diffstat (limited to 'chapter05')
| -rw-r--r-- | chapter05/gcc-exp.xml | 2 | ||||
| -rw-r--r-- | chapter05/patch-exp.xml | 2 | ||||
| -rw-r--r-- | chapter05/shellutils-inst.xml | 2 |
3 files changed, 3 insertions, 3 deletions
diff --git a/chapter05/gcc-exp.xml b/chapter05/gcc-exp.xml index dc2e67bf2..b1fd52b43 100644 --- a/chapter05/gcc-exp.xml +++ b/chapter05/gcc-exp.xml @@ -25,7 +25,7 @@ This is the equivalent to make LDFLAGS=-static as we use with other packages to compile them statically.</para> <para><userinput>ln -s gcc $LFS/static/bin/cc:</userinput> This -creates the $LFS/static/bin/gcc symlink which some packages need.</para> +creates the $LFS/static/bin/gcc symlink, which some packages need.</para> </sect2> diff --git a/chapter05/patch-exp.xml b/chapter05/patch-exp.xml index fc87079f0..0c71ff135 100644 --- a/chapter05/patch-exp.xml +++ b/chapter05/patch-exp.xml @@ -4,7 +4,7 @@ <para><userinput>CPPFLAGS=-D_GNU_SOURCE: </userinput> This flag fixes installation problems of this package on PPC and m68k platforms (that we know of). It doesn't hurt compilation on other -platforms (such as x86); so we do it by default.</para> +platforms, such as x86, so we do it by default.</para> </sect2> diff --git a/chapter05/shellutils-inst.xml b/chapter05/shellutils-inst.xml index 9c31de806..c13dea8c3 100644 --- a/chapter05/shellutils-inst.xml +++ b/chapter05/shellutils-inst.xml @@ -5,7 +5,7 @@ applied. This patch is needed to avoid a conflict of variable names with certain Glibc versions (usually glibc-2.1.x) when compiling sh-utils statically. It is however safe to apply the patch even if you are running -a different glibc version, so if you aren't sure, it's best to apply +a different glibc version. So, if you aren't sure, it's best to apply it.</para> <para><screen><userinput>patch -Np1 -i ../sh-utils-&sh-utils-version;.patch</userinput></screen></para> |