diff options
Diffstat (limited to 'chapter05/glibc.xml')
-rw-r--r-- | chapter05/glibc.xml | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/chapter05/glibc.xml b/chapter05/glibc.xml index 5b5f1d77e..1340cc9c0 100644 --- a/chapter05/glibc.xml +++ b/chapter05/glibc.xml @@ -90,7 +90,7 @@ so:</para> system, in particular the kernel. Additionally, here in this chapter some tests can be adversely affected by existing tools or environmental issues on the host system. Of course, these won't be a problem when we run the Glibc test suite -inside the chroot environment of <xref linkend="chapter06"/>. In general, the +inside the chroot environment of <xref linkend="chapter-building-system"/>. In general, the Glibc test suite is always expected to pass. However, as mentioned above, some failures are unavoidable in certain circumstances. Here is a list of the most common issues we are aware of:</para> @@ -117,9 +117,9 @@ fail due to test timeouts being exceeded.</para></listitem> </itemizedlist> <para>In summary, don't worry too much if you see Glibc test suite failures -here in this chapter. The Glibc in <xref linkend="chapter06"/> is the one we'll +here in this chapter. The Glibc in <xref linkend="chapter-building-system"/> is the one we'll ultimately end up using so that is the one we would really like to see pass. -But please keep in mind, even in <xref linkend="chapter06"/> some failures +But please keep in mind, even in <xref linkend="chapter-building-system"/> some failures could still occur -- the <emphasis>math</emphasis> tests for example. When experiencing a failure, make a note of it, then continue by reissuing the <command>make check</command>. The test suite |