r2233 - / trunk/BOOK/final-system/common trunk/BOOK/final-system/multilib

jim at linuxfromscratch.org jim at linuxfromscratch.org
Sat Aug 19 16:47:00 PDT 2006


Author: jim
Date: 2006-08-19 17:46:58 -0600 (Sat, 19 Aug 2006)
New Revision: 2233

Modified:
   /
   trunk/BOOK/final-system/common/glibc.xml
   trunk/BOOK/final-system/multilib/glibc-64bit.xml
Log:
 r5137 at server (orig r2362):  ken | 2006-08-19 14:37:19 -0700
 Add details of where to look if glibc tests fail, and move posix/annexc out of the paragraph on math tests.



Property changes on: 
___________________________________________________________________
Name: svk:merge
   - b6734a72-470d-0410-b049-f317dca95413:/:2361
   + b6734a72-470d-0410-b049-f317dca95413:/:2362

Modified: trunk/BOOK/final-system/common/glibc.xml
===================================================================
--- trunk/BOOK/final-system/common/glibc.xml	2006-08-19 23:46:47 UTC (rev 2232)
+++ trunk/BOOK/final-system/common/glibc.xml	2006-08-19 23:46:58 UTC (rev 2233)
@@ -104,18 +104,22 @@
 <screen os="n"><userinput>make -k check >glibc-check-log 2>&1 ; grep Error glibc-check-log</userinput></screen>
 
     <para os="o">The Glibc test suite is highly dependent on certain functions of
-    the 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. This is a list of the most common
-    issues:</para>
+    the host system, in particular the kernel. The posix/annexc test normally fails
+    and you should see <literal>Error 1 (ignored)</literal> in the output. Apart
+    from this, the Glibc test suite is always expected to pass. However, in certain
+    circumstances, some failures are unavoidable. If a test fails because of a missing
+    program (or missing symbolic link), or a segfault, you will see an error code
+    greater than 127 and the details will be in the log. More commonly, tests will
+    fail with <literal>Error 2</literal> - for these, the contents of the corresponding
+    <filename>.out</filename> file, e.g. <filename>posix/annexc.out</filename> may be
+    informative. Here is a list of the most common issues:</para>
 
     <itemizedlist os="p">
       <listitem>
         <para>The <emphasis>math</emphasis> tests, at least on i686, fail in
         the <emphasis>test-double</emphasis> and <emphasis>test-idouble</emphasis>
-        tests with gcc-&gcc-version;, the <command>grep</command> command will
-        also report an expected (ignored) failure in <emphasis>posix/annexc
-        </emphasis>. These two failures in the math tests appear to be harmless.
+        tests with gcc-&gcc-version;
+        . These two failures in the math tests appear to be harmless.
         The math tests may also fail 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>

Modified: trunk/BOOK/final-system/multilib/glibc-64bit.xml
===================================================================
--- trunk/BOOK/final-system/multilib/glibc-64bit.xml	2006-08-19 23:46:47 UTC (rev 2232)
+++ trunk/BOOK/final-system/multilib/glibc-64bit.xml	2006-08-19 23:46:58 UTC (rev 2233)
@@ -105,11 +105,9 @@
     href="glibc.xml"
     xpointer="xpointer(//*[@os='n'])"/>
 
-    <para os="o">The Glibc test suite is highly dependent on certain functions of
-    the 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. This is a list of the most common
-    issues:</para>
+    <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
+    href="glibc.xml"
+    xpointer="xpointer(//*[@os='o'])"/>
 
     <itemizedlist os="p">
       <listitem>




More information about the cross-lfs mailing list