Changeset 4fa86d1 for chapter05

Timestamp:

09/29/2003 06:08:10 AM (21 years ago)

Author:

Greg Schafer <greg@…>

Branches:

10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 12.2, 12.2-rc1, 6.0, 6.1, 6.1.1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, v5_0, v5_1, v5_1_1, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/loongarch-12.2, xry111/mips64el, xry111/multilib, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc

Children:

05ed965

Parents:

c1cfddf

Message:

Chapter 5 - Glibc: Add notes regarding test suite issues.

git-svn-id: ​http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2903 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

File:

• chapter05/glibc-inst.xml (modified) (2 diffs)

chapter05/glibc-inst.xml

@@ -78 +78 @@
 
 <para>The missing or incompatible <filename>msgfmt</filename> program is
-generally harmless and shouldn't cause us any problems.</para>
+generally harmless, but it's believed it can sometimes cause problems when
+running the test suite.</para>
 
-<para>Continue with compiling the package:</para>
+<para>Compile the package:</para>
 
-<para><screen><userinput>make
-make check
-make install</userinput></screen></para>
+<para><screen><userinput>make</userinput></screen></para>
 
-<para>The glibc make check process is highly dependent on certain functions
-of your host operating system.  The most common is a host that fails to mount
-a tmpfs filesystem at /dev/shm, which may cause glibc tests to fail.</para>
+<para>Run the test suite:</para>
 
-<para>The locales (used by Glibc to make your Linux system respond in a
-different language) weren't installed when you ran the previous command,
-so we have to do that ourselves now:</para>
+<para><screen><userinput>make check</userinput></screen></para>
+
+<para>The Glibc test suite is highly dependent on certain functions of your host
+system, in particular the kernel. Additionally, here in Chapter 5, 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 Chapter 6. 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>
+
+<itemizedlist>
+<listitem><para>The math tests sometimes fail when running on systems where the 
+CPU is not a relatively new genuine Intel or genuine AMD. Certain optimization
+settings are also known to be a factor here.</para></listitem>
+
+<listitem><para>The gettext test sometimes fails due to host system issues. The
+exact reasons are not yet clear.</para></listitem>
+
+<listitem><para>The atime test sometimes fails when the LFS parition is mounted
+with the noatime option or due to other file system quirks.</para></listitem>
+
+<listitem><para>In general, when running on slower hardware, some tests might
+fail due to test timeouts being exceeded.</para></listitem>
+
+<listitem><para>The shm test might fail in the circumstances of the host system
+running the devfs file system but not having the tmpfs filesystem mounted at
+/dev/shm due to lack of support for tmpfs in the kernel.</para></listitem>
+</itemizedlist>
+
+<para>In summary, don't worry too much if you see Glibc test suite failures here
+in Chapter 5. The Glibc in Chapter 6 is the one we'll ultimately end up using so
+that is the one we would really like to pass. But please keep in mind, even in
+Chapter 6 some failures could still occur, the math tests for example. When
+experiencing a failure, note the failure then continue on by reissuing the
+<userinput>make check</userinput>. The test suite should pick up where it left
+off and continue on. You can circumvent this stop-start sequence by issuing a
+<userinput>make -k check</userinput>. But If you do that, be sure to log the
+output so that you can later on peruse the log file and examine the total number
+of failures.</para>
+
+<para>Now install the package:</para>
+
+<para><screen><userinput>make install</userinput></screen></para>
+
+<para>Different countries and cultures have varying conventions for how to
+communicate. These conventions range from very simple ones, such as the format
+for representing dates and times, to very complex ones, such as the language
+spoken. This "internationalization" works by means of locales. We'll install the
+Glibc locales now:</para>
 
 <para><screen><userinput>make localedata/install-locales</userinput></screen></para>
@@ -100 +144 @@
 <userinput>localedef</userinput> command. Information on this can be
 found in the <filename>INSTALL</filename> file in the
-<filename>glibc-&glibc-version;</filename> tree. However, there are a
+<filename>glibc-&glibc-version;</filename> source. However, there are a
 number of locales that are essential for the tests of future packages
 to pass correctly, in particular, the libstdc++ tests from GCC.  The following 
-instructions, in place of the install-locales command above, will install 
+instructions, instead of the install-locales command above, will install 
 the minimum set of locales necessary for the tests to run successfully:</para>