Changeset 443cace


Ignore:
Timestamp:
01/17/2004 01:37:37 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:
51fe215
Parents:
b05a831
Message:

Implemented changes to make the running of the Chapter 5 test
suites strictly optional i.e. the default action for the
average reader is to not run them. Closes 719.

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

Files:
7 edited

Legend:

Unmodified
Added
Removed

  • chapter01/changelog.xml

    rb05a831 r443cace  
    5151</listitem>
    5252
     53<listitem><para>January 16th, 2004 [greg]: Implemented changes to make the
     54running of the Chapter 5 test suites strictly optional i.e. the default action
     55for the average reader is to not run them. Closes 719.</para></listitem>
     56
    5357<listitem><para>January 13th, 2004 [greg]: Chapter 8 - Installation of the
    5458kernel: Added command to keep a copy of the kernel .config

  • chapter05/binutils-pass1.xml

    rb05a831 r443cace  
    1717because both Glibc and GCC perform various tests on the available linker and
    1818assembler to determine which of their own features to enable.</para>
    19 
    20 <note><para>Even though Binutils is an important toolchain package, we are not
    21 going to run the test suite at this early stage. First, the test suite framework
    22 is not yet in place and second, the programs from this first pass will soon be
    23 overwritten by those installed in the second pass.</para></note>
    2419
    2520<para>This package is known to behave badly when you have changed its default
    … …  
    7873</itemizedlist>
    7974
     75<para>Compilation is now complete. This is the point where we would normally
     76run the test suite. But as discussed earlier, we don't recommend running the
     77test suites for the temporary tools here in this chapter. However, even if we
     78still wanted to run the Binutils test suite, we're unable do so at this early
     79stage because the test suite framework is not yet in place. Not only that, the
     80programs from this first pass will soon be overwritten by those installed in
     81the second pass.</para>
     82
    8083<para>And install the package:</para>
    8184

  • chapter05/binutils-pass2.xml

    rb05a831 r443cace  
    4141<screen><userinput>make</userinput></screen>
    4242
    43 <note><para>It's worth pointing out that running the Binutils test suite here
    44 is considered not as important as running it in
    45 <xref linkend="chapter06"/>.</para></note>
    46 
    47 <para>Test the results (there should be no unexpected failures here, expected
    48 failures are fine):</para>
     43<para>Compilation is now complete. As discussed earlier, we don't recommend
     44running the test suites for the temporary tools here in this chapter. If you
     45still want to run the Binutils test suite anyway, the following command will
     46do so:</para>
    4947
    5048<screen><userinput>make check</userinput></screen>
    5149
    52 <para>Unfortunately, there is no easy way to view the test results summary like
     50<para>There should be no unexpected failures here, expected failures are fine.
     51Unfortunately, there is no easy way to view the test results summary like
    5352there was for the previous GCC package. However, if a failure occurs here, it
    5453should be easy to spot. The output shown will contain something like:</para>

  • chapter05/gcc-pass1.xml

    rb05a831 r443cace  
    1818<para>Unpack only the GCC-core tarball, as we won't be needing a C++ compiler
    1919for the moment.</para>
    20 
    21 <note><para>Even though GCC is an important toolchain package, we are not
    22 going to run the test suite at this early stage. First, the test suite framework
    23 is not yet in place and second, the programs from this first pass will soon be
    24 overwritten by those installed in the second pass.</para></note>
    2520
    2621<para>This package is known to behave badly when you have changed its
    … …  
    8479</itemizedlist>
    8580
     81<para>Compilation is now complete. This is the point where we would normally
     82run the test suite. But as discussed earlier, we don't recommend running the
     83test suites for the temporary tools here in this chapter. However, even if we
     84still wanted to run the GCC test suite, we're unable do so at this early stage
     85because the test suite framework is not yet in place. Not only that, the
     86programs from this first pass will soon be overwritten by those installed in
     87the second pass.</para>
     88
    8689<para>And install the package:</para>
    8790

  • chapter05/gcc-pass2.xml

    rb05a831 r443cace  
    1616<para>The tools required to test GCC and Binutils are installed now (Tcl, Expect
    1717and DejaGnu). We can continue on rebuilding GCC and Binutils, link them against
    18 the new Glibc, and test them properly. One thing to note, however, is that these
    19 test suites are highly dependent on properly functioning pseudo terminals (PTYs)
    20 which are provided by your host distribution. These days, PTYs are most commonly
    21 implemented via the <emphasis>devpts</emphasis> file system. You can quickly
    22 check if your host system is set up correctly in this regard by performing a
    23 simple test:</para>
     18the new Glibc, and test them properly (if performing the test suites in this
     19chapter). One thing to note, however, is that these test suites are highly
     20dependent on properly functioning pseudo terminals (PTYs) which are provided by
     21your host distribution. These days, PTYs are most commonly implemented via the
     22<emphasis>devpts</emphasis> file system. You can quickly check if your host
     23system is set up correctly in this regard by performing a simple test:</para>
    2424
    2525<screen><userinput>expect -c "spawn ls"</userinput></screen>
    … …  
    117117version of the GCC sources we used earlier.</para>
    118118
    119 <note><para>It's worth pointing out that running the GCC test suite here
    120 is considered not as important as running it in
    121 <xref linkend="chapter06"/>.</para></note>
    122 
    123 <para>Test the results:</para>
     119<para>Compilation is now complete. As discussed earlier, we don't recommend
     120running the test suites for the temporary tools here in this chapter. If you
     121still want to run the GCC test suite anyway, the following command will do
     122so:</para>
    124123
    125124<screen><userinput>make -k check</userinput></screen>

  • chapter05/glibc.xml

    rb05a831 r443cace  
    1818Glibc-linuxthreads in that directory, not in the directory where you usually
    1919unpack all the sources.</para>
    20 
    21 <note><para>We are going to run the test suite for Glibc in this chapter.
    22 However, it's worth pointing out that running the Glibc test suite here
    23 is considered not as important as running it in
    24 <xref linkend="chapter06"/>.</para></note>
    2520
    2621<para>This package is known to behave badly when you have changed its
    … …  
    8984<screen><userinput>make</userinput></screen>
    9085
    91 <para>Run the test suite:</para>
     86<para>Compilation is now complete. As discussed earlier, we don't recommend
     87running the test suites for the temporary system here in this chapter. If you
     88still want to run the Glibc test suite anyway, the following command will do
     89so:</para>
    9290
    9391<screen><userinput>make check</userinput></screen>
    … …  
    150148for representing dates and times, to very complex ones, such as the language
    151149spoken. The "internationalization" of GNU programs works by means of
    152 <emphasis>locales</emphasis>. We'll install the Glibc locales now:</para>
     150<emphasis>locales</emphasis>.</para>
     151
     152<note><para>If you are not running the test suites here in this chapter as per
     153our recommendation, there is little point in installing the locales now. We'll
     154be installing the locales in the next chapter.</para></note>
     155
     156<para>If you still want to install the Glibc locales anyway, the following
     157command will do so:</para>
    153158
    154159<screen><userinput>make localedata/install-locales</userinput></screen>

  • chapter05/tcl.xml

    rb05a831 r443cace  
    1919test suites for GCC and Binutils. Installing three packages just for testing
    2020purposes may seem like overkill, but it is very reassuring, if not essential,
    21 to know that our most important tools are working properly.</para>
     21to know that our most important tools are working properly. Even if you are
     22not running the test suites here in this chapter as per our recommendation,
     23these packages are still required for the test suites in the next
     24chapter.</para>
    2225
    2326<para>Prepare Tcl for compilation:</para>
Note: See TracChangeset for help on using the changeset viewer.