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

removed chapter 5 glibc test suite

Browse Source 
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@8641 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
DJ Lucas 2008-10-11 23:39:51 +00:00
parent 5c92d210d5
commit 0abc697e29
2 changed files with 6 additions and 31 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
chapter01/changelog.xml
View File

@ -40,6 +40,10 @@
<listitem> <listitem>
<para>2008-10-11</para> <para>2008-10-11</para>
<itemizedlist> <itemizedlist>
<listitem>
<para>[dj] - Removed the chapter 5 glibc test suite information as
it requires a working C++ compiler to run.</para>
</listitem>
<listitem> <listitem>
<para>[randy] - Added three configure parameters to the Chapter 6 <para>[randy] - Added three configure parameters to the Chapter 6
Util-linux-ng instructions so that additional programs are Util-linux-ng instructions so that additional programs are

33
chapter05/glibc.xml
View File

@ -43,12 +43,6 @@
<sect2 role="installation"> <sect2 role="installation">
<title>Installation of Glibc</title> <title>Installation of Glibc</title>
<para>Though not mandatory in this chapter, if you plan on running the test
suite, you should apply the following patches:</para>
<screen><userinput remap="pre">patch -Np1 -i ../&glibc-iconv-test-fixes-patch;
patch -Np1 -i ../&glibc-ildoubl-test-fix-patch;</userinput></screen>
<para>The Glibc documentation recommends building Glibc outside of the source <para>The Glibc documentation recommends building Glibc outside of the source
directory in a dedicated build directory:</para> directory in a dedicated build directory:</para>
@ -163,31 +157,8 @@ cd ../glibc-build</userinput></screen>
<screen><userinput remap="make">make</userinput></screen> <screen><userinput remap="make">make</userinput></screen>
<para>Compilation is now complete. As mentioned earlier, running the <para>This package does come with a test suite, however, it cannot be
test suites for the temporary tools installed in this chapter is not run at this time because we do not have a C++ compiler yet.</para>
mandatory. To run the Glibc test suite (if desired), the following
commands will do so:</para>
<screen><userinput remap="test">cp -v ../glibc-&glibc-version;/iconvdata/gconv-modules iconvdata
make check</userinput></screen>
<para>For a discussion of test failures that are of particular
importance, please see <xref linkend="ch-system-glibc" role="."/></para>
<para>In this chapter, some tests can be adversely affected by
existing tools or environmental issues on the host system. Glibc test
suite failures in this chapter are typically not worrisome. The Glibc
installed in <xref linkend="chapter-building-system"/> is the one that
will ultimately end up being used, so that is the one that needs to pass
most tests (even in <xref linkend="chapter-building-system"/>, some
failures could still occur, for example, with the math tests).</para>
<para>When experiencing a failure, make a note of it, then continue by
reissuing the <command>make check</command> command. The test suite
should pick up where it left off and continue. This stop-start sequence
can be circumvented by issuing a <command>make -k check</command> command.
If using this option, be sure to log the output so that the log file can
be examined for failures later.</para>
<para>The install stage of Glibc will issue a harmless warning at the <para>The install stage of Glibc will issue a harmless warning at the
end about the absence of <filename>/tools/etc/ld.so.conf</filename>. end about the absence of <filename>/tools/etc/ld.so.conf</filename>.