Changeset bea9517 for final-preps


Ignore:
Timestamp:
Feb 21, 2006, 2:04:25 AM (17 years ago)
Author:
Jim Gifford <clfs@…>
Children:
f9b5055
Parents:
4799507
Message:

r1023@server (orig r1021): chris | 2006-01-08 00:36:31 -0800
Rewrote description of build process and test suite info, and added mention of test suites to some packages.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • final-preps/abouttestsuites.xml

    r4799507 rbea9517  
    1111  <title>About the Test Suites</title>
    1212
    13   <para>TO BE REWRITTEN (and maybe moved to final-system chapter)</para>
    14 
    1513  <para>Most packages provide a test suite. Running the test suite for a
    1614  newly built package is a good idea because it can provide a <quote>sanity
     
    2018  that the package is totally bug free.</para>
    2119
    22   <para>Some test suites are more important than others. For example,
    23   the test suites for the core toolchain packages&mdash;GCC, Binutils, and
    24   Glibc&mdash;are of the utmost importance due to their central role in a
    25   properly functioning system. The test suites for GCC and Glibc can
    26   take a very long time to complete, especially on slower hardware, but
    27   are strongly recommended.</para>
    28 
    29   <note>
    30     <para>It is not possible to run testsuites when cross-compiling, so there
    31     are no instructions given for running testsuites until
    32     <xref linkend="chapter-building-system"/>.</para>
    33   </note>
    34 
    35   <para>A common issue with running the test suites for Binutils and GCC
    36   is running out of pseudo terminals (PTYs). This can result in a high
    37   number of failing tests. This may happen for several reasons, but the
    38   most likely cause is that the host system does not have the
    39   <systemitem class="filesystem">devpts</systemitem> file system set up
    40   correctly. This issue is discussed in greater detail at
    41   <ulink url="http://www.linuxfromscratch.org/lfs/faq.html#no-ptys"/>.</para>
    42 
    43   <para>Sometimes package test suites will fail, but for reasons which the
    44   developers are aware of and have deemed non-critical. Consult the logs located
    45   at <ulink url="&test-results;"/> to verify whether or not these failures are
    46   expected. This site is valid for all tests throughout this book.</para>
     20  <para>It is not possible to run testsuites when cross-compiling, so package installation instructions do not explain how to run testsuites until <xref linkend="chapter-building-system"/>.</para>
    4721
    4822</sect1>
Note: See TracChangeset for help on using the changeset viewer.