diff options
| author | Matthew Burgess <matthew@linuxfromscratch.org> | 2005-05-12 21:46:28 +0000 |
|---|---|---|
| committer | Matthew Burgess <matthew@linuxfromscratch.org> | 2005-05-12 21:46:28 +0000 |
| commit | 296762cd02ce492bdbd6c889b94bbe6974c34f41 (patch) | |
| tree | 47956cec364fc077cd278a6c76c24d516de722ce /chapter05 | |
| parent | a86df627670f914d4e75076e4ee99385fa67f4fc (diff) | |
Wording and tagging improvements
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@5318 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Diffstat (limited to 'chapter05')
| -rw-r--r-- | chapter05/glibc.xml | 2 | ||||
| -rw-r--r-- | chapter05/toolchaintechnotes.xml | 4 |
2 files changed, 3 insertions, 3 deletions
diff --git a/chapter05/glibc.xml b/chapter05/glibc.xml index d49d870c7..8b166917b 100644 --- a/chapter05/glibc.xml +++ b/chapter05/glibc.xml @@ -144,7 +144,7 @@ command will do so:</para> <para>For a discussion of test failures that are of particular importance, please see <xref linkend="ch-system-glibc" role="."/></para> -<para>In this chapter, some tests can be adversely effected by +<para>In this chapter, some tests can be adversely affected by existing tools or environmental issues on the host system. Glibc test suite failures in this chapter are typically not worrisome. The Glibc installed in <xref linkend="chapter-building-system"/> is the one that diff --git a/chapter05/toolchaintechnotes.xml b/chapter05/toolchaintechnotes.xml index 9a065a054..5b2522458 100644 --- a/chapter05/toolchaintechnotes.xml +++ b/chapter05/toolchaintechnotes.xml @@ -66,7 +66,7 @@ search path ensures programs are linked only against chosen libraries</para></listitem> <listitem><para>Careful manipulation of <command>gcc</command>'s -<filename>specs</filename> file tell the compiler which target dynamic +<filename>specs</filename> file tells the compiler which target dynamic linker will be used</para></listitem> </itemizedlist> @@ -77,7 +77,7 @@ software features to enable or disable. This is more important than one might first realize. An incorrectly configured GCC or Glibc can result in a subtly broken toolchain, where the impact of such breakage might not show up until near the end of the build of an entire -distribution. A test suite failure will usually alert this error +distribution. A test suite failure will usually highlight this error before too much additional work is performed.</para> <para>Binutils installs its assembler and linker in two locations, |