Changeset 31b2ae6


Ignore:
Timestamp:
01/16/2004 10:15:49 AM (20 years ago)
Author:
Greg Schafer <greg@…>
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, 6.0, 6.1, 6.1.1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 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, v5_1, v5_1_1, 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:
b05a831
Parents:
0b43834
Message:

First stage towards Bug 719. Making the Chapter 5 test suites
strictly optional.

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

Files:
14 edited

Legend:

Unmodified
Added
Removed

  • chapter02/abouttestsuites.xml

    r0b43834 r31b2ae6  
    1717hardware.</para>
    1818
     19<para>Experience has shown us that there is little to be gained from running
     20the test suites in Chapter 5. There can be no escaping the fact that the host
     21system always exerts influence on the Chapter 5 tests, often causing weird and
     22inexplicable failures. Not only that, the tools built in Chapter 5 are
     23temporary and eventually discarded. For the average reader of this book we
     24recommend not to run the Chapter 5 test suites. The instructions for running
     25the Chapter 5 test suites are still provided for the benefit of testers and
     26developers but they are strictly optional for everyone else.</para>
     27
    1928<para>As you progress through the book and encounter the build commands to
    2029run the various test suites, we'll guide you on the relative importance of

  • chapter05/bash.xml

    r0b43834 r31b2ae6  
    2727<screen><userinput>make</userinput></screen>
    2828
    29 <para>This package has a test suite available which can perform a number of
    30 checks to ensure it built correctly.  Should you choose to run it, the
    31 following command will do so:</para>
     29<para>As discussed earlier, we don't recommend running the test suites for the
     30temporary tools here in this chapter. If you still want to run the Bash test
     31suite anyway, the following command will do so:</para>
    3232
    3333<screen><userinput>make tests</userinput></screen>

  • chapter05/coreutils.xml

    r0b43834 r31b2ae6  
    2424<screen><userinput>make</userinput></screen>
    2525
    26 <para>This package has a test suite available which can perform a number of
    27 checks to ensure it built correctly.  Should you choose to run it, the
    28 following command will do so:</para>
     26<para>As discussed earlier, we don't recommend running the test suites for the
     27temporary tools here in this chapter. If you still want to run the Coreutils
     28test suite anyway, the following command will do so:</para>
    2929
    3030<screen><userinput>make RUN_EXPENSIVE_TESTS=yes check</userinput></screen>

  • chapter05/expect.xml

    r0b43834 r31b2ae6  
    4545<screen><userinput>make</userinput></screen>
    4646
    47 <para>This package has a test suite available which can perform a number of
    48 checks to ensure it built correctly. However, the Expect test suite
    49 is known to experience failures under certain host conditions that
    50 are not fully understood. Therefore, test suite failures here are not
    51 surprising, and are not considered critical. Should you choose to run the test
    52 suite, the following command will do so:</para>
     47<para>As discussed earlier, we don't recommend running the test suites for the
     48temporary tools here in this chapter. If you still want to run the Expect test
     49suite anyway, the following command will do so. However, you should be aware
     50that the Expect test suite is sometimes known to experience failures under
     51certain host conditions that are not fully understood. Therefore, test suite
     52failures here are not surprising, but are not considered critical:</para>
    5353
    5454<screen><userinput>make test</userinput></screen>

  • chapter05/findutils.xml

    r0b43834 r31b2ae6  
    2222<screen><userinput>make</userinput></screen>
    2323
    24 <para>This package has a test suite available which can perform a number of
    25 checks to ensure it built correctly.  Should you choose to run it, the
    26 following command will do so:</para>
     24<para>As discussed earlier, we don't recommend running the test suites for the
     25temporary tools here in this chapter. If you still want to run the Findutils
     26test suite anyway, the following command will do so:</para>
    2727
    2828<screen><userinput>make check</userinput></screen>

  • chapter05/gawk.xml

    r0b43834 r31b2ae6  
    2424<screen><userinput>make</userinput></screen>
    2525
    26 <para>This package has a test suite available which can perform a number of
    27 checks to ensure it built correctly. Should you choose to run it, the
    28 following command will do so:</para>
     26<para>As discussed earlier, we don't recommend running the test suites for the
     27temporary tools here in this chapter. If you still want to run the Gawk test
     28suite anyway, the following command will do so:</para>
    2929
    3030<screen><userinput>make check</userinput></screen>

  • chapter05/gettext.xml

    r0b43834 r31b2ae6  
    2222<screen><userinput>make</userinput></screen>
    2323
    24 <para>This package has a test suite available which can perform a number of
    25 checks to ensure it built correctly. However, the Gettext test suite is known
    26 to experience failures under certain host conditions -- for
    27 example, if it finds a Java compiler on the host (Note: an experimental patch
    28 to disable Java is available from the patches project). The Gettext test suite
    29 takes a very long time to run and is not considered critical. Therefore,
    30 we don't recommend running it here. Should you choose to run it, the following
    31 command will do so:</para>
     24<para>As discussed earlier, we don't recommend running the test suites for the
     25temporary tools here in this chapter. If you still want to run the Gettext test
     26suite anyway, the following command will do so. However, you should be aware
     27that the Gettext test suite is known to experience failures under certain host
     28conditions -- for example, when it finds a Java compiler on the host (Note: an
     29experimental patch to disable Java is available from the patches project). Not
     30only that, the Gettext test suite takes an excessive amount of time to run and
     31is not considered critical:</para>
    3232
    3333<screen><userinput>make check</userinput></screen>

  • chapter05/grep.xml

    r0b43834 r31b2ae6  
    3535<screen><userinput>make</userinput></screen>
    3636
    37 <para>This package has a test suite available which can perform a number of
    38 checks to ensure it built correctly.  Should you choose to run it, the
    39 following command will do so:</para>
     37<para>As discussed earlier, we don't recommend running the test suites for the
     38temporary tools here in this chapter. If you still want to run the Grep test
     39suite anyway, the following command will do so:</para>
    4040
    4141<screen><userinput>make check</userinput></screen>

  • chapter05/make.xml

    r0b43834 r31b2ae6  
    2222<screen><userinput>make</userinput></screen>
    2323
    24 <para>This package has a test suite available which can perform a number of
    25 checks to ensure it built correctly.  Should you choose to run it, the
    26 following command will do so:</para>
     24<para>As discussed earlier, we don't recommend running the test suites for the
     25temporary tools here in this chapter. If you still want to run the Make test
     26suite anyway, the following command will do so:</para>
    2727
    2828<screen><userinput>make check</userinput></screen>

  • chapter05/sed.xml

    r0b43834 r31b2ae6  
    2222<screen><userinput>make</userinput></screen>
    2323
    24 <para>This package has a test suite available which can perform a number of
    25 checks to ensure it built correctly.  Should you choose to run it, the
    26 following command will do so:</para>
     24<para>As discussed earlier, we don't recommend running the test suites for the
     25temporary tools here in this chapter. If you still want to run the Sed test
     26suite anyway, the following command will do so:</para>
    2727
    2828<screen><userinput>make check</userinput></screen>

  • chapter05/tar.xml

    r0b43834 r31b2ae6  
    2222<screen><userinput>make</userinput></screen>
    2323
    24 <para>This package has a test suite available which can perform a number of
    25 checks to ensure it built correctly.  Should you choose to run it, the
    26 following command will do so:</para>
     24<para>As discussed earlier, we don't recommend running the test suites for the
     25temporary tools here in this chapter. If you still want to run the Tar test
     26suite anyway, the following command will do so:</para>
    2727
    2828<screen><userinput>make check</userinput></screen>

  • chapter05/tcl.xml

    r0b43834 r31b2ae6  
    3030<screen><userinput>make</userinput></screen>
    3131
    32 <para>This package has a test suite available which can perform a number of
    33 checks to ensure it built correctly. However, the Tcl test suite in this
    34 chapter is known to experience failures under certain host conditions that are
    35 not fully understood. Therefore, test suite failures here are not surprising,
    36 but are not considered critical. Should you choose to run the test suite, the
    37 following command will do so:</para>
     32<para>As discussed earlier, we don't recommend running the test suites for the
     33temporary tools here in this chapter. If you still want to run the Tcl test
     34suite anyway, the following command will do so. However, you should be aware
     35that the Tcl test suite is sometimes known to experience failures under certain
     36host conditions that are not fully understood. Therefore, test suite failures
     37here are not surprising, but are not considered critical:</para>
    3838
    3939<screen><userinput>TZ=UTC make test</userinput></screen>

  • chapter05/texinfo.xml

    r0b43834 r31b2ae6  
    2222<screen><userinput>make</userinput></screen>
    2323
    24 <para>This package has a test suite available which can perform a number of
    25 checks to ensure it built correctly.  Should you choose to run it, the
    26 following command will do so:</para>
     24<para>As discussed earlier, we don't recommend running the test suites for the
     25temporary tools here in this chapter. If you still want to run the Texinfo test
     26suite anyway, the following command will do so:</para>
    2727
    2828<screen><userinput>make check</userinput></screen>

  • index.xml

    r0b43834 r31b2ae6  
    33                        "/usr/share/docbook/docbookx.dtd" [
    44
    5 <!ENTITY version "CVS-2004-01-14">
    6 <!ENTITY releasedate "January 14th, 2004">
     5<!ENTITY version "CVS-2004-01-16">
     6<!ENTITY releasedate "January 16th, 2004">
    77<!ENTITY milestone "5.1">
    88<!ENTITY nbsp " ">
Note: See TracChangeset for help on using the changeset viewer.