diff options
author | Zack Winkles <winkie@linuxfromscratch.org> | 2004-05-03 21:28:58 +0000 |
---|---|---|
committer | Zack Winkles <winkie@linuxfromscratch.org> | 2004-05-03 21:28:58 +0000 |
commit | 9dfc02ff38f26117daffe7d8b822ebb64a3fed04 (patch) | |
tree | c3ea0521973ac75238f6ab5f674d5b4fc4032df8 /chapter05/binutils-pass2.xml | |
parent | 411ceb86b8150183a447f89b4789395bf16fddf0 (diff) |
Current BE-LFS (but w/ GCC 3.3.3) merged -> 6.0 branch
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@3445 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Diffstat (limited to 'chapter05/binutils-pass2.xml')
-rw-r--r-- | chapter05/binutils-pass2.xml | 13 |
1 files changed, 12 insertions, 1 deletions
diff --git a/chapter05/binutils-pass2.xml b/chapter05/binutils-pass2.xml index 32c749b77..78436e1b0 100644 --- a/chapter05/binutils-pass2.xml +++ b/chapter05/binutils-pass2.xml @@ -50,7 +50,16 @@ running the test suites for the temporary tools here in this chapter. If nevertheless you want to run the Binutils test suite, the following command will do so:</para> -<screen><userinput>make check</userinput></screen> +<screen><userinput>make -k check</userinput></screen> + +<para>Except for a few known failures, the binutils tests should all pass. The +exceptions to this rule are as follows:</para> + +<screen>* 5 FAIL (unexpected failure) for visibility +* 1 FAIL for selective4 +* 1 FAIL for selective5</screen> + +<!-- <para>There should be no unexpected failures here, expected failures are fine. Unfortunately, there is no easy way to view the test results summary like there @@ -59,6 +68,8 @@ to spot. The output shown will contain something like:</para> <blockquote><screen>make[1]: *** [check-binutils] Error 2</screen></blockquote> +--> + <para>And install the package:</para> <screen><userinput>make install</userinput></screen> |