Changeset c91dd5b


Ignore:
Timestamp:
02/11/2004 10:02:10 PM (20 years ago)
Author:
Alex Gronenwoud <alex@…>
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:
a0b689e
Parents:
5cd6caa
Message:

Making the test suites in chapter 5 more clearly optional.

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

Files:
17 edited

Legend:

Unmodified
Added
Removed

  • appendixa/expect-shortdesc.xml

    r5cd6caa rc91dd5b  
    55<para><emphasis>Installed program</emphasis>: expect</para>
    66
    7 <para><emphasis>Installed library</emphasis>: libexpect5.39.a</para>
     7<para><emphasis>Installed library</emphasis>: libexpect&expect-version;.a</para>
    88
    99</sect2>

  • chapter02/abouttestsuites.xml

    r5cd6caa rc91dd5b  
    66built package is generally a good idea, as it can provide a nice sanity check
    77that everything compiled correctly. A test suite that passes its set of checks
    8 usually proves that the package is functioning mostly as the developer
    9 intended. It does not, however, guarantee that the package is totally bug
    10 free.</para>
     8usually proves that the package is functioning as the developer intended. It
     9does not, however, guarantee that the package is totally bug free.</para>
    1110
    1211<para>Some test suites are more important than others. For example, the test
    13 suites for the core toolchain packages -- GCC, Binutils, and Glibc (the C
    14 library) -- are of the utmost importance due to their central role in a
    15 properly functioning system. But be warned, the test suites for GCC and Glibc
    16 can take a very long time to complete, especially on slower hardware.</para>
     12suites for the core toolchain packages -- GCC, Binutils, and Glibc -- are of
     13the utmost importance due to their central role in a properly functioning
     14system. But be warned, the test suites for GCC and Glibc can take a very long
     15time to complete, especially on slower hardware.</para>
    1716
    18 <para>Experience has shown us that there is little to be gained from running
    19 the test suites in <xref linkend="chapter-temporary-tools"/>. There can be no escaping the
    20 fact that the host system always exerts influence on the tests in that chapter,
    21 often causing weird and inexplicable failures. Not only that, the tools built
    22 in <xref linkend="chapter-temporary-tools"/> are temporary and eventually discarded. For the
    23 average reader of this book we recommend <emphasis>not</emphasis> to run the
    24 test suites in <xref linkend="chapter-temporary-tools"/>. The instructions for running those
    25 test suites are still provided for the benefit of testers and developers, but
    26 they are strictly optional for everyone else.</para>
     17<note><para>Experience has shown us that there is little to be gained from running
     18the test suites in <xref linkend="chapter-temporary-tools"/>. There can be no
     19escaping the fact that the host system always exerts some influence on the
     20tests in that chapter, often causing weird and inexplicable failures. Not only
     21that, the tools built in <xref linkend="chapter-temporary-tools"/> are
     22temporary and eventually discarded. For the average reader of this book we
     23recommend <emphasis>not</emphasis> to run the test suites in <xref
     24linkend="chapter-temporary-tools"/>. The instructions for running those test
     25suites are still provided for the benefit of testers and developers, but they
     26are strictly optional for everyone else.</para></note>
    2727
    28 <para>As you progress through the book and encounter the commands to run the
    29 various test suites, we'll guide you on the relative importance of the test
    30 suite in question, so that you can decide for yourself whether to run that one
    31 or not.</para>
     28<para>A common problem when running the test suites for Binutils and GCC is
     29running out of pseudo terminals (PTYs for short). The symptom is a very high
     30number of failing tests. This can happen for several reasons, but the most
     31likely cause is that the host system doesn't have the
     32<emphasis>devpts</emphasis> file system set up correctly. We'll discuss this in
     33more detail later on in <xref linkend="chapter-temporary-tools"/>.</para>
    3234
    33 <note><para>A common problem when running the test suites for Binutils and GCC
    34 is running out of pseudo terminals (PTYs for short). The symptom is an
    35 unusually high number of failing tests. This can happen for a number of
    36 reasons. Most likely is that the host system doesn't have the
    37 <emphasis>devpts</emphasis> file system set up correctly. We'll discuss this in
    38 more detail later on in <xref linkend="chapter-temporary-tools"/>.</para></note>
     35<para>Sometimes package test suites will give false failures. You can
     36consult the LFS Wiki at <ulink url="&wiki-root;"/> to verify that these
     37failures are normal. This applies to all tests throughout the book.</para>
    3938
    4039</sect1>

  • chapter04/chapter04.xml

    r5cd6caa rc91dd5b  
    168168
    169169Make (&make-version;) - &make-size;:
    170 <ulink url="http://freshmeat.net/projects/gnumake"/>
     170<ulink url="http://freshmeat.net/projects/gnumake/"/>
    171171
    172172Make_devices (&makedev-version;) - &makedev-size;:

  • chapter05/bash.xml

    r5cd6caa rc91dd5b  
    2727<screen><userinput>make</userinput></screen>
    2828
    29 <para>As discussed earlier, we don't recommend running the test suites for the
    30 temporary tools here in this chapter. If you still want to run the Bash test
    31 suite anyway, the following command will do so:</para>
    32 
    33 <screen><userinput>make tests</userinput></screen>
     29<para>(If you insist on testing the results, then issue:
     30<userinput>make tests</userinput>.)</para>
    3431
    3532<para>Then install it and its documentation:</para>

  • chapter05/coreutils.xml

    r5cd6caa rc91dd5b  
    1919
    2020<para>Coreutils has an issue when compiled against Glibc-&glibc-version;.
    21 Without the patch below, some of the Coreutils utilities (head, tail, sort etc)
    22 will reject their traditional syntax which has been in use for approximately 30
    23 years. The old syntax is so pervasive that compatibility must be preserved until
    24 the many places where it is used can be updated. More details are provided in
    25 the comments inside the patch itself. Use of this patch is by no means
    26 compulsory but opting not to use it means you'll have deal with the consequences
    27 yourself, i.e. patch the many software packages that use the old syntax. Apply
    28 the patch:</para>
     21Without the patch below, some of the Coreutils utilities
     22(<command>head</command>, <command>tail</command>, <command>sort</command>,
     23and others) will reject their traditional syntax which has been in use for
     24approximately 30 years. This old syntax is so pervasive that compatibility
     25should be preserved until the many places where it is used can be updated.
     26More details on this are provided in the comments inside the patch itself. Use
     27of this patch is by no means compulsory, but not using it means you'll have to
     28deal with the consequences yourself: patch the many packages that use the old
     29syntax. Therefore, better apply the patch:</para>
    2930
    3031<screen><userinput>patch -Np1 -i ../&coreutils-posixver-patch;</userinput></screen>
    … …  
    3839<screen><userinput>make</userinput></screen>
    3940
    40 <para>As discussed earlier, we don't recommend running the test suites for the
    41 temporary tools here in this chapter. If you still want to run the Coreutils
    42 test suite anyway, the following command will do so:</para>
    43 
    44 <screen><userinput>make RUN_EXPENSIVE_TESTS=yes check</userinput></screen>
    45 
    46 <para>The meaning of the make parameter:</para>
    47 
    48 <itemizedlist>
    49 <listitem><para><userinput>RUN_EXPENSIVE_TESTS=yes</userinput>: This tells the
    50 test suite to run several additional tests that are considered relatively
    51 expensive on some platforms. However, they are generally not a problem on
    52 Linux.</para></listitem>
    53 </itemizedlist>
     41<para>(If you insist on testing the results, then issue:
     42<userinput>make RUN_EXPENSIVE_TESTS=yes check</userinput>. The
     43<emphasis>RUN_EXPENSIVE_TESTS=yes</emphasis> parameter tells the test suite to
     44run several additional tests that are considered relatively expensive on some
     45platforms but generally are not a problem on Linux.)</para>
    5446
    5547<para>And install the package:</para>

  • chapter05/expect.xml

    r5cd6caa rc91dd5b  
    4545<screen><userinput>make</userinput></screen>
    4646
    47 <para>As discussed earlier, we don't recommend running the test suites for the
    48 temporary tools here in this chapter. If you still want to run the Expect test
    49 suite anyway, the following command will do so. However, you should be aware
    50 that the Expect test suite is sometimes known to experience failures under
    51 certain host conditions that are not fully understood. Therefore, test suite
    52 failures here are not surprising, but are not considered critical:</para>
     47<para>(If you insist on testing the results, then issue:
     48<userinput>make test</userinput>. However, the Expect test suite is known to
     49experience failures under certain host conditions that are not fully
     50understood. Therefore, test suite failures here are not surprising, and are not
     51considered critical.)</para>
    5352
    54 <screen><userinput>make test</userinput></screen>
    55 
    56 <para>And install:</para>
     53<para>And install it:</para>
    5754
    5855<screen><userinput>make SCRIPTS="" install</userinput></screen>

  • chapter05/findutils.xml

    r5cd6caa rc91dd5b  
    2222<screen><userinput>make</userinput></screen>
    2323
    24 <para>As discussed earlier, we don't recommend running the test suites for the
    25 temporary tools here in this chapter. If you still want to run the Findutils
    26 test suite anyway, the following command will do so:</para>
    27 
    28 <screen><userinput>make check</userinput></screen>
     24<para>(If you insist on testing the results, then issue:
     25<userinput>make check</userinput>.)</para>
    2926
    3027<para>And install the package:</para>

  • chapter05/gawk.xml

    r5cd6caa rc91dd5b  
    2424<screen><userinput>make</userinput></screen>
    2525
    26 <para>As discussed earlier, we don't recommend running the test suites for the
    27 temporary tools here in this chapter. If you still want to run the Gawk test
    28 suite anyway, the following command will do so:</para>
    29 
    30 <screen><userinput>make check</userinput></screen>
     26<para>(If you insist on testing the results, then issue:
     27<userinput>make check</userinput>.)</para>
    3128
    3229<para>And install it:</para>

  • chapter05/gettext.xml

    r5cd6caa rc91dd5b  
    2222<screen><userinput>make</userinput></screen>
    2323
    24 <para>As discussed earlier, we don't recommend running the test suites for the
    25 temporary tools here in this chapter. If you still want to run the Gettext test
    26 suite anyway, the following command will do so. However, you should be aware
    27 that the Gettext test suite is known to experience failures under certain host
    28 conditions -- for example, when it finds a Java compiler on the host (Note: an
    29 experimental patch to disable Java is available from the patches project). Not
    30 only that, the Gettext test suite takes an excessive amount of time to run and
    31 is not considered critical:</para>
    32 
    33 <screen><userinput>make check</userinput></screen>
     24<para>(If you insist on testing the results, then issue: <userinput>make
     25check</userinput>. This takes a very long time, around 6 SBUs. Moreover, the
     26Gettext test suite is known to experience failures under certain host
     27conditions -- for example when it finds a Java compiler on the host (but an
     28experimental patch to disable Java is available from the LFS Patches
     29project).)</para>
    3430
    3531<para>And install the package:</para>

  • chapter05/grep.xml

    r5cd6caa rc91dd5b  
    3535<screen><userinput>make</userinput></screen>
    3636
    37 <para>As discussed earlier, we don't recommend running the test suites for the
    38 temporary tools here in this chapter. If you still want to run the Grep test
    39 suite anyway, the following command will do so:</para>
    40 
    41 <screen><userinput>make check</userinput></screen>
     37<para>(If you insist on testing the results, then issue:
     38<userinput>make check</userinput>.)</para>
    4239
    4340<para>Then install them and their documentation:</para>

  • chapter05/kernelheaders.xml

    r5cd6caa rc91dd5b  
    3939cp -R include/asm-generic /tools/include</userinput></screen>
    4040
    41 <para>Install the cross-platform kernel header files:</para>
     41<para>And finally install the cross-platform kernel header files:</para>
    4242
    4343<screen><userinput>cp -R include/linux /tools/include</userinput></screen>

  • chapter05/make.xml

    r5cd6caa rc91dd5b  
    2222<screen><userinput>make</userinput></screen>
    2323
    24 <para>As discussed earlier, we don't recommend running the test suites for the
    25 temporary tools here in this chapter. If you still want to run the Make test
    26 suite anyway, the following command will do so:</para>
    27 
    28 <screen><userinput>make check</userinput></screen>
     24<para>(If you insist on testing the results, then issue:
     25<userinput>make check</userinput>.)</para>
    2926
    3027<para>Then install it and its documentation:</para>

  • chapter05/patch.xml

    r5cd6caa rc91dd5b  
    1414<title>Installation of Patch</title>
    1515
    16 <para>Prepare Patch for compilation:</para>
     16<para>Prepare Patch for compilation (the preprocessor flag
     17<emphasis>-D_GNU_SOURCE</emphasis> is only needed on the PowerPC platform, on
     18other architectures you can leave it out):</para>
    1719
    1820<screen><userinput>CPPFLAGS=-D_GNU_SOURCE ./configure --prefix=/tools</userinput></screen>
    19 
    20 <para>The preprocessor flag <emphasis>-D_GNU_SOURCE</emphasis> is only needed
    21 on the PowerPC platform. On other architectures you can leave it out.</para>
    2221
    2322<para>Compile the program:</para>

  • chapter05/sed.xml

    r5cd6caa rc91dd5b  
    2222<screen><userinput>make</userinput></screen>
    2323
    24 <para>As discussed earlier, we don't recommend running the test suites for the
    25 temporary tools here in this chapter. If you still want to run the Sed test
    26 suite anyway, the following command will do so:</para>
    27 
    28 <screen><userinput>make check</userinput></screen>
     24<para>(If you insist on testing the results, then issue:
     25<userinput>make check</userinput>.)</para>
    2926
    3027<para>Then install it and its documentation:</para>

  • chapter05/tar.xml

    r5cd6caa rc91dd5b  
    2222<screen><userinput>make</userinput></screen>
    2323
    24 <para>As discussed earlier, we don't recommend running the test suites for the
    25 temporary tools here in this chapter. If you still want to run the Tar test
    26 suite anyway, the following command will do so:</para>
    27 
    28 <screen><userinput>make check</userinput></screen>
     24<para>(If you insist on testing the results, then issue:
     25<userinput>make check</userinput>.)</para>
    2926
    3027<para>Then install them and their documentation:</para>

  • chapter05/tcl.xml

    r5cd6caa rc91dd5b  
    3333<screen><userinput>make</userinput></screen>
    3434
    35 <para>As discussed earlier, we don't recommend running the test suites for the
    36 temporary tools here in this chapter. If you still want to run the Tcl test
    37 suite anyway, the following command will do so. However, you should be aware
    38 that the Tcl test suite is sometimes known to experience failures under certain
    39 host conditions that are not fully understood. Therefore, test suite failures
    40 here are not surprising, but are not considered critical:</para>
    41 
    42 <screen><userinput>TZ=UTC make test</userinput></screen>
    43 
    44 <para>The meaning of the make parameter:</para>
    45 
    46 <itemizedlist>
    47 <listitem><para><userinput>TZ=UTC</userinput>: This sets the time zone to
    48 Coordinated Universal Time (UTC) also known as Greenwich Mean Time (GMT), but
    49 only for the duration of the test suite run. This ensures the clock tests are
    50 exercised correctly. More information on the TZ environment variable will be
    51 given later on in <xref linkend="chapter-bootscripts"/>.</para></listitem>
    52 </itemizedlist>
    53 
    54 <para>Sometimes package test suites will give false failures. You can
    55 consult the LFS Wiki at <ulink url="&wiki-root;"/> to verify that these
    56 failures are normal. This applies to all tests throughout the book.</para>
     35<para>(If you insist on testing the results, then issue:
     36<userinput>TZ=UTC make test</userinput>. However, the Tcl test suite is known
     37to experience failures under certain host conditions that are not fully
     38understood. Therefore, test suite failures here are not surprising, and are not
     39considered critical. The <emphasis>TZ=UTC</emphasis> parameter sets the time
     40zone to Coordinated Universal Time (UTC) also known as Greenwich Mean Time
     41(GMT), but only for the duration of the test suite run. This ensures the clock
     42tests are exercised correctly. More information on the TZ environment variable
     43will be given later on in <xref linkend="chapter-bootscripts"/>.)</para>
    5744
    5845<para>Install the package:</para>
    … …  
    7057<literallayout></literallayout>
    7158
    72 <para>Make a necessary symbolic link:</para>
     59<para>And make a necessary symbolic link:</para>
    7360
    7461<screen><userinput>ln -s tclsh8.4 /tools/bin/tclsh</userinput></screen>

  • chapter05/texinfo.xml

    r5cd6caa rc91dd5b  
    2222<screen><userinput>make</userinput></screen>
    2323
    24 <para>As discussed earlier, we don't recommend running the test suites for the
    25 temporary tools here in this chapter. If you still want to run the Texinfo test
    26 suite anyway, the following command will do so:</para>
    27 
    28 <screen><userinput>make check</userinput></screen>
     24<para>(If you insist on testing the results, then issue:
     25<userinput>make check</userinput>.)</para>
    2926
    3027<para>Then install them and their documentation:</para>
Note: See TracChangeset for help on using the changeset viewer.