aboutsummaryrefslogtreecommitdiffstats
path: root/chapter04/abouttestsuites.xml
diff options
context:
space:
mode:
Diffstat (limited to 'chapter04/abouttestsuites.xml')
-rw-r--r--chapter04/abouttestsuites.xml10
1 files changed, 5 insertions, 5 deletions
diff --git a/chapter04/abouttestsuites.xml b/chapter04/abouttestsuites.xml
index 9206f33be..459472be0 100644
--- a/chapter04/abouttestsuites.xml
+++ b/chapter04/abouttestsuites.xml
@@ -27,21 +27,21 @@
<note>
<para>Running the test suites in <xref linkend="chapter-cross-tools"/>
and <xref linkend="chapter-temporary-tools"/>
- is impossible, since the programs are compiled with a cross-compiler,
- so are not supposed to be able to run on the build host.</para>
+ is pointless; since the test programs are compiled with a cross-compiler,
+ they probably can't run on the build host.</para>
</note>
<para>A common issue with running the test suites for binutils and GCC
- is running out of pseudo terminals (PTYs). This can result in a high
+ is running out of pseudo terminals (PTYs). This can result in a large
number of failing tests. This may happen for several reasons, but the
most likely cause is that the host system does not have the
<systemitem class="filesystem">devpts</systemitem> file system set up
correctly. This issue is discussed in greater detail at
<ulink url="&lfs-root;lfs/faq.html#no-ptys"/>.</para>
- <para>Sometimes package test suites will fail, but for reasons which the
+ <para>Sometimes package test suites will fail for reasons which the
developers are aware of and have deemed non-critical. Consult the logs located
at <ulink url="&test-results;"/> to verify whether or not these failures are
- expected. This site is valid for all tests throughout this book.</para>
+ expected. This site is valid for all test suites throughout this book.</para>
</sect1>