aboutsummaryrefslogtreecommitdiffstats
path: root/chapter05/coreutils.xml
diff options
context:
space:
mode:
Diffstat (limited to 'chapter05/coreutils.xml')
-rw-r--r--chapter05/coreutils.xml36
1 files changed, 14 insertions, 22 deletions
diff --git a/chapter05/coreutils.xml b/chapter05/coreutils.xml
index cea1f6fd6..6672e18d5 100644
--- a/chapter05/coreutils.xml
+++ b/chapter05/coreutils.xml
@@ -18,14 +18,15 @@ And for the patch:
<title>Installation of Coreutils</title>
<para>Coreutils has an issue when compiled against Glibc-&glibc-version;.
-Without the patch below, some of the Coreutils utilities (head, tail, sort etc)
-will reject their traditional syntax which has been in use for approximately 30
-years. The old syntax is so pervasive that compatibility must be preserved until
-the many places where it is used can be updated. More details are provided in
-the comments inside the patch itself. Use of this patch is by no means
-compulsory but opting not to use it means you'll have deal with the consequences
-yourself, i.e. patch the many software packages that use the old syntax. Apply
-the patch:</para>
+Without the patch below, some of the Coreutils utilities
+(<command>head</command>, <command>tail</command>, <command>sort</command>,
+and others) will reject their traditional syntax which has been in use for
+approximately 30 years. This old syntax is so pervasive that compatibility
+should be preserved until the many places where it is used can be updated.
+More details on this are provided in the comments inside the patch itself. Use
+of this patch is by no means compulsory, but not using it means you'll have to
+deal with the consequences yourself: patch the many packages that use the old
+syntax. Therefore, better apply the patch:</para>
<screen><userinput>patch -Np1 -i ../&coreutils-posixver-patch;</userinput></screen>
@@ -37,20 +38,11 @@ the patch:</para>
<screen><userinput>make</userinput></screen>
-<para>As discussed earlier, we don't recommend running the test suites for the
-temporary tools here in this chapter. If you still want to run the Coreutils
-test suite anyway, the following command will do so:</para>
-
-<screen><userinput>make RUN_EXPENSIVE_TESTS=yes check</userinput></screen>
-
-<para>The meaning of the make parameter:</para>
-
-<itemizedlist>
-<listitem><para><userinput>RUN_EXPENSIVE_TESTS=yes</userinput>: This tells the
-test suite to run several additional tests that are considered relatively
-expensive on some platforms. However, they are generally not a problem on
-Linux.</para></listitem>
-</itemizedlist>
+<para>(If you insist on testing the results, then issue:
+<userinput>make RUN_EXPENSIVE_TESTS=yes check</userinput>. The
+<emphasis>RUN_EXPENSIVE_TESTS=yes</emphasis> parameter tells the test suite to
+run several additional tests that are considered relatively expensive on some
+platforms but generally are not a problem on Linux.)</para>
<para>And install the package:</para>