|
|
@@ -117,53 +117,29 @@ running the test suite.</para>
|
|
|
|
|
|
<screen><userinput>make</userinput></screen>
|
|
|
|
|
|
-<para>Compilation is now complete. As mentioned earlier, we don't recommend
|
|
|
-running the test suites for the temporary system here in this chapter. If you
|
|
|
-still want to run the Glibc test suite anyway, the following command will do
|
|
|
-so:</para>
|
|
|
+<para>Compilation is now complete. As mentioned earlier, running the test suites
|
|
|
+for the temporary tools installed in this chapter is not mandatory. If you want
|
|
|
+to run the Glibc test suite though, the following command will do so:</para>
|
|
|
|
|
|
<screen><userinput>make check</userinput></screen>
|
|
|
|
|
|
-<para>The Glibc test suite is highly dependent on certain functions of your host
|
|
|
-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="chapter-building-system"/>. In
|
|
|
-general, the Glibc test suite is always expected to pass. However, as mentioned
|
|
|
-above, in certain circumstances some failures are unavoidable. Here is a list
|
|
|
-of the most common issues we are aware of:</para>
|
|
|
-
|
|
|
-<itemizedlist>
|
|
|
-<listitem><para>The <emphasis>math</emphasis> tests sometimes fail when running
|
|
|
-on systems where the CPU is not a relatively new genuine Intel or authentic AMD.
|
|
|
-Certain optimization settings are also known to be a factor here.</para></listitem>
|
|
|
-
|
|
|
-<listitem><para>The <emphasis>gettext</emphasis> test sometimes fails due to
|
|
|
-host system issues. The exact reasons are not yet clear.</para></listitem>
|
|
|
-
|
|
|
-<listitem><para>The <emphasis>atime</emphasis> test sometimes fails when the
|
|
|
-LFS partition is mounted with the <parameter>noatime</parameter> option, or due
|
|
|
-to other file system quirks.</para></listitem>
|
|
|
-
|
|
|
-<listitem><para>The <emphasis>shm</emphasis> test might fail when the host
|
|
|
-system is running the devfs file system but doesn't have the <systemitem class="filesystem">tmpfs</systemitem> file system
|
|
|
-mounted at <filename class="directory">/dev/shm</filename> due to lack of support for tmpfs in
|
|
|
-the kernel.</para></listitem>
|
|
|
-
|
|
|
-<listitem><para>When running on older and slower hardware, some tests might
|
|
|
-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="chapter-building-system"/> is
|
|
|
-the one we'll ultimately end up using, so that is the one we would really like
|
|
|
-to see pass the tests (but even there 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 should pick up where it left off and continue.
|
|
|
-You can circumvent this stop-start sequence by issuing a <command>make -k
|
|
|
-check</command>. But if you do that, be sure to log the output so that you can
|
|
|
-later peruse the log file and examine the total number of failures.</para>
|
|
|
+<para>For a discussion of test failures that are of particular
|
|
|
+importance, please see <xref linkend="ch-system-glibc"/>.</para>
|
|
|
+
|
|
|
+<para>In this chapter, some tests can be adversely affected by existing tools or
|
|
|
+environmental issues on the host system. In short, don't worry too much if you
|
|
|
+see Glibc test suite failures 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 the tests (but even
|
|
|
+there some failures could still occur -- the <emphasis>math</emphasis> tests,
|
|
|
+for example).</para>
|
|
|
+
|
|
|
+<para>When experiencing a failure, make a note of it, then continue by reissuing
|
|
|
+the <command>make check</command>. The test suite should pick up where it left
|
|
|
+off and continue. You can circumvent this stop-start sequence by issuing a
|
|
|
+<command>make -k check</command>. If you do that though, be sure to log the
|
|
|
+output so that you can later peruse the log file and examine the total number of
|
|
|
+failures.</para>
|
|
|
|
|
|
<para>Though it is a harmless message, the install stage of Glibc will at the
|
|
|
end complain about the absence of <filename>/tools/etc/ld.so.conf</filename>.
|
Matthew Burgess