diff options
| author | Greg Schafer <greg@linuxfromscratch.org> | 2003-10-01 11:14:11 +0000 |
|---|---|---|
| committer | Greg Schafer <greg@linuxfromscratch.org> | 2003-10-01 11:14:11 +0000 |
| commit | bd10d482480b7ce74c00c400019d93a4f48fedd2 (patch) | |
| tree | 98c535aa2e1b359c62e7c990c1987adfef3835de | |
| parent | a6ab2e7cb75d36f5292e2764bc66208024b9081f (diff) | |
Add some clarifying text re test suites.
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2912 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
| -rw-r--r-- | chapter05/binutils-pass2-inst.xml | 3 | ||||
| -rw-r--r-- | chapter05/gcc-pass2-inst.xml | 7 |
2 files changed, 8 insertions, 2 deletions
diff --git a/chapter05/binutils-pass2-inst.xml b/chapter05/binutils-pass2-inst.xml index 0f465ba12..d4c4bae67 100644 --- a/chapter05/binutils-pass2-inst.xml +++ b/chapter05/binutils-pass2-inst.xml @@ -33,7 +33,8 @@ variables that override the default optimization flags.</para> <para><screen><userinput>make </userinput></screen></para> -<para>Test the results (nothing should fail here):</para> +<para>Test the results (there should be no unexpected failures here, expected +failures are fine):</para> <para><screen><userinput>make check</userinput></screen></para> diff --git a/chapter05/gcc-pass2-inst.xml b/chapter05/gcc-pass2-inst.xml index 71eadbaa0..1a26bfb5a 100644 --- a/chapter05/gcc-pass2-inst.xml +++ b/chapter05/gcc-pass2-inst.xml @@ -131,7 +131,7 @@ current GCC-3.3.1 should look on i686-pc-linux-gnu, see <para>Note that the results contain:</para> <screen>* 1 XPASS (unexpected pass) for g++ -* 1 FAIL for g++ +* 1 FAIL (unexpected failure) for g++ * 2 FAIL for gcc * 26 XPASS's for libstdc++</screen> @@ -148,6 +148,11 @@ model (which may be applicable if for instance you were using Newlibc, Sun-libc or whatever libc). The libstdc++ test suite is apparently expecting the "generic" model, hence those tests are not always expected to pass.</para> +<para>Unexpected failures often cannot be avoided. The GCC developers are +usually aware of them but haven't yet gotten around to fixing them. In short, +unless your results are vastly different from those at the above URL, it is safe +to continue on.</para> + <para>And finally install the package:</para> <para><screen><userinput>make install</userinput></screen></para> |