aboutsummaryrefslogtreecommitdiffstats
path: root/chapter05/gcc-pass2.xml
diff options
context:
space:
mode:
authorAlex Gronenwoud <alex@linuxfromscratch.org>2004-02-04 22:22:49 +0000
committerAlex Gronenwoud <alex@linuxfromscratch.org>2004-02-04 22:22:49 +0000
commitfe5b13b40b50e7be2b16cbd477988e7828fcd8ca (patch)
tree33b61713c805145912ed919b77ef1db620e3d6de /chapter05/gcc-pass2.xml
parent4248b0ec1488319d448ad624e275a9a2811c0090 (diff)
Moving Mounting proc to before Chroot, dropping Util-linux, adding an arch script to Perl.
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@3220 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Diffstat (limited to 'chapter05/gcc-pass2.xml')
-rw-r--r--chapter05/gcc-pass2.xml2
1 files changed, 1 insertions, 1 deletions
diff --git a/chapter05/gcc-pass2.xml b/chapter05/gcc-pass2.xml
index 982c267d6..462f92f0b 100644
--- a/chapter05/gcc-pass2.xml
+++ b/chapter05/gcc-pass2.xml
@@ -128,7 +128,7 @@ through to completion and not stop at the first failure. The GCC test suite is
very comprehensive and is almost guaranteed to generate a few failures. To get
a summary of the test suite results, run this:</para>
-<screen><userinput>../&gcc-dir;/contrib/test_summary | more</userinput></screen>
+<screen><userinput>../&gcc-dir;/contrib/test_summary | grep -A7 Summ</userinput></screen>
<para>You can compare your results to those posted to the gcc-testresults
mailing list for similar configurations to your own. For an example of how