|
|
@@ -105,21 +105,21 @@ 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
|
|
|
+<listitem><para>The atime test sometimes fails when the LFS partition 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
|
|
|
+running the devfs file system but not having the tmpfs file system 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
|
|
|
+that is the one we would really like to see 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
|
Greg Schafer