aboutsummaryrefslogtreecommitdiffstats
path: root/chapter04/abouttestsuites.xml
diff options
context:
space:
mode:
Diffstat (limited to 'chapter04/abouttestsuites.xml')
-rw-r--r--chapter04/abouttestsuites.xml11
1 files changed, 6 insertions, 5 deletions
diff --git a/chapter04/abouttestsuites.xml b/chapter04/abouttestsuites.xml
index 780216181..9206f33be 100644
--- a/chapter04/abouttestsuites.xml
+++ b/chapter04/abouttestsuites.xml
@@ -18,19 +18,20 @@
that the package is totally bug free.</para>
<para>Some test suites are more important than others. For example,
- the test suites for the core toolchain packages&mdash;GCC, Binutils, and
- Glibc&mdash;are of the utmost importance due to their central role in a
- properly functioning system. The test suites for GCC and Glibc can
+ the test suites for the core toolchain packages&mdash;GCC, binutils, and
+ glibc&mdash;are of the utmost importance due to their central role in a
+ properly functioning system. The test suites for GCC and glibc can
take a very long time to complete, especially on slower hardware, but
are strongly recommended.</para>
<note>
- <para>Running the test suites in <xref linkend="chapter-temporary-tools"/>
+ <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>
</note>
- <para>A common issue with running the test suites for Binutils and GCC
+ <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
number of failing tests. This may happen for several reasons, but the
most likely cause is that the host system does not have the