Browse Source

Update known regression test failures for gcc and glibc.

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@10906 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Bruce Dubbs 10 years ago
parent
commit
0238d4951e
2 changed files with 7 additions and 18 deletions
  1. 2 14
      chapter06/gcc.xml
  2. 5 4
      chapter06/glibc.xml

+ 2 - 14
chapter06/gcc.xml

@@ -40,17 +40,7 @@
 
 
   <sect2 role="installation">
   <sect2 role="installation">
     <title>Installation of GCC</title>
     <title>Installation of GCC</title>
-<!--
-    <para>As in Chapter 5, fix a problem identified upstream:</para>
 
 
-<screen><userinput remap="pre">sed -i 's/if \((code.*))\)/if (\1 \&amp;\&amp; \!DEBUG_INSN_P (insn))/' gcc/sched-deps.c</userinput></screen>
-
-
-    <para>Now fix another problem identified upstream that causes some 
-    programs to fail:</para>
-
-<screen><userinput remap="pre">patch -Np1 -i ../&gcc-upstream-patch;</userinput></screen>
--->
     <para>The GCC documentation recommends building GCC outside of the source
     <para>The GCC documentation recommends building GCC outside of the source
     directory in a dedicated build directory:</para>
     directory in a dedicated build directory:</para>
 
 
@@ -121,10 +111,8 @@ cd ../gcc-build</userinput></screen>
     url="&test-results;"/> and <ulink url="http://gcc.gnu.org/ml/gcc-testresults/"/>.</para>
     url="&test-results;"/> and <ulink url="http://gcc.gnu.org/ml/gcc-testresults/"/>.</para>
 
 
     <para>A few unexpected failures cannot always be avoided. The GCC developers
     <para>A few unexpected failures cannot always be avoided. The GCC developers
-    are usually aware of these issues, but have not resolved them yet. <!-- In
-    particular, the <filename class="libraryfile">libmudflap</filename> tests
-    are known to be particularly problematic as a result of a bug in GCC
-    (<ulink url="http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20003"/>). -->
+    are usually aware of these issues, but have not resolved them yet.
+    In particular, four tests in the libgomp test suite are known to fail.
     Unless the test results are vastly different from those at the above URL,
     Unless the test results are vastly different from those at the above URL,
     it is safe to continue.</para>
     it is safe to continue.</para>
 
 

+ 5 - 4
chapter06/glibc.xml

@@ -118,6 +118,11 @@ cd ../glibc-build</userinput></screen>
 
 
     <itemizedlist>
     <itemizedlist>
 
 
+      <listitem>
+        <para>posix/tst-getaddrinfo4 will always fail 
+        due to not having a network connection when the tests are run.</para>
+      </listitem>
+
       <listitem>
       <listitem>
         <para>The <emphasis>tst/tst-cputimer1</emphasis> and 
         <para>The <emphasis>tst/tst-cputimer1</emphasis> and 
         <emphasis>rt/tst-cpuclock2</emphasis> tests have been known to
         <emphasis>rt/tst-cpuclock2</emphasis> tests have been known to
@@ -139,10 +144,6 @@ cd ../glibc-build</userinput></screen>
         make -k check</command>).</para>
         make -k check</command>).</para>
       </listitem>
       </listitem>
 -->
 -->
-      <listitem>
-        <para>posix/tst-getaddrinfo4 and posix/tst-getaddrinfo5 will always fail 
-        due to not having a network connection when the tests are run.</para>
-      </listitem>
 <!--
 <!--
       <listitem>
       <listitem>
         <para>libio/tst-ftell-partial-wide.out fails because it needs a locale
         <para>libio/tst-ftell-partial-wide.out fails because it needs a locale