diff options
| -rw-r--r-- | chapter01/changelog.xml | 5 | ||||
| -rw-r--r-- | chapter05/bash.xml | 2 | ||||
| -rw-r--r-- | chapter05/binutils-pass2.xml | 7 | ||||
| -rw-r--r-- | chapter05/coreutils.xml | 2 | ||||
| -rw-r--r-- | chapter05/expect.xml | 10 | ||||
| -rw-r--r-- | chapter05/findutils.xml | 2 | ||||
| -rw-r--r-- | chapter05/gawk.xml | 2 | ||||
| -rw-r--r-- | chapter05/gcc-pass2.xml | 6 | ||||
| -rw-r--r-- | chapter05/gettext.xml | 2 | ||||
| -rw-r--r-- | chapter05/glibc.xml | 64 | ||||
| -rw-r--r-- | chapter05/grep.xml | 2 | ||||
| -rw-r--r-- | chapter05/make.xml | 2 | ||||
| -rw-r--r-- | chapter05/sed.xml | 2 | ||||
| -rw-r--r-- | chapter05/tar.xml | 2 | ||||
| -rw-r--r-- | chapter05/texinfo.xml | 2 | ||||
| -rw-r--r-- | chapter06/glibc.xml | 27 | ||||
| -rw-r--r-- | general.ent | 4 |
17 files changed, 72 insertions, 71 deletions
diff --git a/chapter01/changelog.xml b/chapter01/changelog.xml index f38dddb20..70c250d0b 100644 --- a/chapter01/changelog.xml +++ b/chapter01/changelog.xml @@ -78,6 +78,11 @@ first a summary, then a detailed log.</para> </itemizedlist> </listitem> +<listitem><para>June 27, 2004 [matt]: Moved glibc test result discussion to +chapter 6 (where it is actually recommended to be run). Also made it clearer +that the tests in chapter 5 are optional, as opposed to +<emphasis>not recommended</emphasis></para></listitem> + <listitem><para>June 26, 2004 [winkie]: Upgraded to GCC 3.4.1-20040625.</para> </listitem> diff --git a/chapter05/bash.xml b/chapter05/bash.xml index a76c56019..b8b9bda09 100644 --- a/chapter05/bash.xml +++ b/chapter05/bash.xml @@ -40,7 +40,7 @@ patch:</para> <screen><userinput>make</userinput></screen> -<para>(If you insist on testing the results, then issue: +<para>(If you want to test the results, then issue: <userinput>make tests</userinput>.)</para> <para>Then install it and its documentation:</para> diff --git a/chapter05/binutils-pass2.xml b/chapter05/binutils-pass2.xml index 7eb1cf670..b09b9fae6 100644 --- a/chapter05/binutils-pass2.xml +++ b/chapter05/binutils-pass2.xml @@ -53,10 +53,9 @@ variables that override the default optimization flags.</para> <screen><userinput>make</userinput></screen> -<para>Compilation is now complete. As discussed earlier, we don't recommend -running the test suites for the temporary tools here in this chapter. If -nevertheless you want to run the Binutils test suite, the following command -will do so:</para> +<para>Compilation is now complete. As discussed earlier, running the test suite +isn't mandatory for the temporary tools here in this chapter. If you do want to +run the Binutils test suite though, the following command will do so:</para> <screen><userinput>make -k check</userinput></screen> diff --git a/chapter05/coreutils.xml b/chapter05/coreutils.xml index 904cc7af3..27eea305f 100644 --- a/chapter05/coreutils.xml +++ b/chapter05/coreutils.xml @@ -50,7 +50,7 @@ above.</para> <screen><userinput>make</userinput></screen> -<para>(If you insist on testing the results, then issue: +<para>(If you want to test the results, then issue: <userinput>make RUN_EXPENSIVE_TESTS=yes check</userinput>. The <parameter>RUN_EXPENSIVE_TESTS=yes</parameter> parameter tells the test suite to run several additional tests that are considered relatively expensive on some diff --git a/chapter05/expect.xml b/chapter05/expect.xml index 274ab0767..2e68a3aba 100644 --- a/chapter05/expect.xml +++ b/chapter05/expect.xml @@ -10,8 +10,8 @@ <indexterm zone="ch-tools-expect"><primary sortas="a-Expect">Expect</primary></indexterm> <sect2 role="package"><title/> -<para>The Expect package contains a program for doing scripted dialogues with -other interactive programs.</para> +<para>The Expect package contains a program for carrying out scripted dialogues +with other interactive programs.</para> <segmentedlist> <segtitle>&buildtime;</segtitle> @@ -61,10 +61,10 @@ libraries, both of which may possibly reside on the host system.</para></listite <screen><userinput>make</userinput></screen> -<para>(If you insist on testing the results, then issue: +<para>(If you want to test the results, then issue: <userinput>make test</userinput>. However, the Expect test suite is known to -experience failures under certain host conditions that are not fully -understood. Therefore, test suite failures here are not surprising, and are not +experience failures under certain host conditions that are not within our +control. Therefore, test suite failures here are not surprising, and are not considered critical.)</para> <para>And install it:</para> diff --git a/chapter05/findutils.xml b/chapter05/findutils.xml index 408daaff4..aa204ccf5 100644 --- a/chapter05/findutils.xml +++ b/chapter05/findutils.xml @@ -35,7 +35,7 @@ <screen><userinput>make</userinput></screen> -<para>(If you insist on testing the results, then issue: +<para>(If you want to test the results, then issue: <userinput>make check</userinput>.)</para> <para>And install the package:</para> diff --git a/chapter05/gawk.xml b/chapter05/gawk.xml index 59a6dab1b..356cf2339 100644 --- a/chapter05/gawk.xml +++ b/chapter05/gawk.xml @@ -35,7 +35,7 @@ <screen><userinput>make</userinput></screen> -<para>(If you insist on testing the results, then issue: +<para>(If you want to test the results, then issue: <userinput>make check</userinput>.)</para> <para>And install it:</para> diff --git a/chapter05/gcc-pass2.xml b/chapter05/gcc-pass2.xml index 8a62c1dcc..d391b7aad 100644 --- a/chapter05/gcc-pass2.xml +++ b/chapter05/gcc-pass2.xml @@ -146,10 +146,8 @@ have no use for it.</para></listitem> as the compiler we're using to compile this GCC was built from the exact same version of the GCC sources we used earlier.</para> -<para>Compilation is now complete. As mentioned earlier, we don't recommend -running the test suites for the temporary tools here in this chapter. If you -still want to run the GCC 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 compiled in this chapter is not mandatory. If you want to run the GCC test suite anyway, the following command will do so:</para> <screen><userinput>make -k check</userinput></screen> diff --git a/chapter05/gettext.xml b/chapter05/gettext.xml index b2174d8f8..d88a1a358 100644 --- a/chapter05/gettext.xml +++ b/chapter05/gettext.xml @@ -56,7 +56,7 @@ which doesn't have a C# compiler.</para></listitem> <screen><userinput>make</userinput></screen> -<para>(If you insist on testing the results, then issue: <userinput>make +<para>(If you want to test the results, then issue: <userinput>make check</userinput>. This takes a very long time, around 7 SBUs. Moreover, the Gettext test suite is known to experience failures under certain host conditions -- for example when it finds a Java compiler on the host (but an diff --git a/chapter05/glibc.xml b/chapter05/glibc.xml index df76dfa1d..b05a59cf1 100644 --- a/chapter05/glibc.xml +++ b/chapter05/glibc.xml @@ -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>. diff --git a/chapter05/grep.xml b/chapter05/grep.xml index 92d2c2337..9fcdaca18 100644 --- a/chapter05/grep.xml +++ b/chapter05/grep.xml @@ -54,7 +54,7 @@ use the code from Glibc, which is known to be slightly buggy.</para></listitem> <screen><userinput>make</userinput></screen> -<para>(If you insist on testing the results, then issue: +<para>(If you want to test the results, then issue: <userinput>make check</userinput>.)</para> <para>Then install them and their documentation:</para> diff --git a/chapter05/make.xml b/chapter05/make.xml index 7a258e1e5..2d8bccdcf 100644 --- a/chapter05/make.xml +++ b/chapter05/make.xml @@ -35,7 +35,7 @@ <screen><userinput>make</userinput></screen> -<para>(If you insist on testing the results, then issue: +<para>(If you want to test the results, then issue: <userinput>make check</userinput>.)</para> <para>Then install it and its documentation:</para> diff --git a/chapter05/sed.xml b/chapter05/sed.xml index 836820b70..ff6975b93 100644 --- a/chapter05/sed.xml +++ b/chapter05/sed.xml @@ -41,7 +41,7 @@ that the original file permissions are preserved.</para> <screen><userinput>make</userinput></screen> -<para>(If you insist on testing the results, then issue: +<para>(If you want to test the results, then issue: <userinput>make check</userinput>.)</para> <para>Then install it and its documentation:</para> diff --git a/chapter05/tar.xml b/chapter05/tar.xml index b8e340be3..62896f359 100644 --- a/chapter05/tar.xml +++ b/chapter05/tar.xml @@ -35,7 +35,7 @@ <screen><userinput>make</userinput></screen> -<para>(If you insist on testing the results, then issue: +<para>(If you want to test the results, then issue: <userinput>make check</userinput>.)</para> <para>Then install them and their documentation:</para> diff --git a/chapter05/texinfo.xml b/chapter05/texinfo.xml index 2b3f742d2..d5e4faeac 100644 --- a/chapter05/texinfo.xml +++ b/chapter05/texinfo.xml @@ -35,7 +35,7 @@ <screen><userinput>make</userinput></screen> -<para>(If you insist on testing the results, then issue: +<para>(If you want to test the results, then issue: <userinput>make check</userinput>.)</para> <para>Then install them and their documentation:</para> diff --git a/chapter06/glibc.xml b/chapter06/glibc.xml index b29676594..0bb5e8cc5 100644 --- a/chapter06/glibc.xml +++ b/chapter06/glibc.xml @@ -79,8 +79,31 @@ circumstance.</para></important> <screen><userinput>make check</userinput></screen> -<para>The test suite notes from <xref linkend="ch-tools-glibc"/> are still very much -appropriate here. Be sure to refer back there should you have any doubts.</para> +<para>The Glibc test suite is highly dependent on certain functions of your host +system, in particular the kernel. In general, the Glibc test suite is always +expected to pass. However, 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>Though it is a harmless message, the install stage of Glibc will complain about the absence of <filename>/etc/ld.so.conf</filename>. Fix this diff --git a/general.ent b/general.ent index 909fa0c38..3affd1634 100644 --- a/general.ent +++ b/general.ent @@ -1,6 +1,6 @@ <?xml version="1.0" encoding="ISO-8859-1"?> -<!ENTITY version "SVN-20040626"> -<!ENTITY releasedate "June 26, 2004"> +<!ENTITY version "SVN-20040627"> +<!ENTITY releasedate "June 27, 2004"> <!ENTITY milestone "6.0"> <!ENTITY lfs-root "http://www.linuxfromscratch.org/"> |