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

File:
1 edited

Legend:

Unmodified
Added
Removed

  • 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>
Note: See TracChangeset for help on using the changeset viewer.