Touch up discussions of regression test failures in a few packages

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

chapter06/automake.xml

@@ -58,8 +58,8 @@
 <screen><userinput remap="test">sed -i "s:./configure:LEXLIB=/usr/lib/libfl.a &amp;:" t/lex-{clean,depend}-cxx.sh
 make -j4 check</userinput></screen>
 
-    <para>Three tests are known to fail in the LFS environment:
-    check12.sh, subobj.sh, and check12-w.sh.</para>
+    <para>Two tests are known to fail in the LFS environment:
+    check12.sh and check12-w.sh.</para>
 
     <para>Install the package:</para>
 

chapter06/gcc.xml

@@ -126,7 +126,7 @@ cd       build</userinput></screen>
 
     <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, five tests in the libstdc++ test suite are known to fail
+    In particular, six tests in the libstdc++ test suite are known to fail
     when running as the root user as we do here.
     Unless the test results are vastly different from those at the above URL,
     it is safe to continue.</para>

chapter06/glibc.xml

@@ -159,12 +159,17 @@ unset GCC_INCDIR</userinput></screen>
 
     <itemizedlist>
 
+      <listitem>
+        <para><emphasis>misc/tst-ttyname</emphasis> 
+        is known to fail in the LFS chroot environment.</para>
+      </listitem>
+
       <listitem>
         <para><emphasis>posix/tst-getaddrinfo4</emphasis> and
         <emphasis>posix/tst-getaddrinfo5</emphasis>
         may fail on some architectures.</para>
       </listitem>
-
+<!--
       <listitem>
         <para>The <emphasis>rt/tst-cputimer1</emphasis> and 
         <emphasis>rt/tst-cpuclock2</emphasis> tests have been known to
@@ -188,7 +193,7 @@ unset GCC_INCDIR</userinput></screen>
         <para>Other tests known to fail on some architectures are
         malloc/tst-malloc-usable and nptl/tst-cleanupx4. </para>
       </listitem>
-
+-->
     </itemizedlist>
 
     <para>Though it is a harmless message, the install stage of Glibc will