Changeset 5d1f0157 for chapter06/glibc.xml

Timestamp:

10/02/2014 07:00:51 AM (10 years ago)

Author:

Bruce Dubbs <bdubbs@…>

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, 7.7, 7.8, 7.9, 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, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc

Children:

4072774

Parents:

82d957c

Message:

Added perl patch to fix CVE-2014-4330.

Update to grub-2.02~beta2. It's been in beta for over 9 months
and a 'stable' does not seem to be forthcoming.

Document glibc tests known to sometimes fail.

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

File:

• chapter06/glibc.xml (modified) (3 diffs)

chapter06/glibc.xml

@@ -116 +116 @@
 
     <itemizedlist>
-<!--
+
       <listitem>
-        <para>The <emphasis>nptl/tst-clock2</emphasis>,
-        <emphasis>nptl/tst-attr3</emphasis>,
-        <emphasis>tst/tst-cputimer1</emphasis>, and
-        <emphasis>rt/tst-cpuclock2</emphasis>
-        tests have been known to fail.  The
-        reason is not completely understood, but indications are that minor
-        timing issues can trigger these failures.</para>
+        <para>The <emphasis>tst/tst-cputimer1</emphasis> test has been known to
+        fail.  The reason is not completely understood, but indications are
+        that minor timing issues can trigger this failure.</para>
       </listitem>
 
@@ -132 +128 @@
         authentic AMD processor.</para>
       </listitem>
-
+<!--
       <listitem>
         <para>When running on older and slower hardware or on systems under
@@ -150 +146 @@
         that has not yet been generated.</para>
       </listitem>
-
+-->
       <listitem>
-        <para>Other tests known to fail on some architectures are posix/bug-regex32,
-        misc/tst-writev, elf/check-textrel, nptl/tst-getpid2, nptl/tst-robust8,
-        and stdio-common/bug22.</para>
+        <para>Other tests known to fail on some architectures are
+        malloc/tst-malloc-usable and  nptl/tst-cleanupx4. </para>
       </listitem>
--->
+
     </itemizedlist>