gronod/lfs
1
0
Fork 0
mirror of https://git.linuxfromscratch.org/lfs.git synced 2025-06-19 03:39:20 +01:00
Code Issues Packages Projects Releases Wiki Activity

Touch up discussions of regression test failures in a few packages

Browse Source 
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@11368 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Bruce Dubbs 2018-02-15 17:21:30 +00:00
parent a3c628a124
commit 751a13dcfb
3 changed files with 10 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
chapter06/automake.xml
View File

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

2
chapter06/gcc.xml
View File

@ -126,7 +126,7 @@ cd build</userinput></screen>
<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. 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. when running as the root user as we do here.
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>

9
chapter06/glibc.xml
View File

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