aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorAlex Gronenwoud <alex@linuxfromscratch.org>2004-02-07 14:55:41 +0000
committerAlex Gronenwoud <alex@linuxfromscratch.org>2004-02-07 14:55:41 +0000
commite8692c5ee76662b25bd502df06818c910bb6aa3b (patch)
treea190144b846f06f7f8ce0d65a0fd41cc698dd36e
parent8a5f9064c4423d2a3217080dd8203c3f7b8391c3 (diff)
Changing 'grep -A7' into a comment.
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@3235 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
-rw-r--r--chapter05/gcc-pass2.xml5
1 files changed, 4 insertions, 1 deletions
diff --git a/chapter05/gcc-pass2.xml b/chapter05/gcc-pass2.xml
index b8dcbaa60..cc7a66822 100644
--- a/chapter05/gcc-pass2.xml
+++ b/chapter05/gcc-pass2.xml
@@ -128,7 +128,10 @@ 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 | grep -A7 Summ</userinput></screen>
+<screen><userinput>../&gcc-dir;/contrib/test_summary</userinput></screen>
+
+<para>(For just the summaries, pipe the output through
+<userinput>grep -A7 Summ</userinput>.)</para>
<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