| 1 | <sect1 id="ch05-coreutils">
|
|---|
| 2 | <title>Installing Coreutils-&coreutils-version;</title>
|
|---|
| 3 | <?dbhtml filename="coreutils.html" dir="chapter05"?>
|
|---|
| 4 |
|
|---|
| 5 | <screen>Estimated build time: &coreutils-time-tools;
|
|---|
| 6 | Estimated required disk space: &coreutils-compsize-tools;</screen>
|
|---|
| 7 |
|
|---|
| 8 | <literallayout>Official download location for Coreutils (&coreutils-version;):
|
|---|
| 9 | <ulink url="ftp://ftp.gnu.org/gnu/coreutils/"/></literallayout>
|
|---|
| 10 |
|
|---|
| 11 | &aa-coreutils-dep;
|
|---|
| 12 |
|
|---|
| 13 | <sect2><title> </title><para> </para></sect2>
|
|---|
| 14 |
|
|---|
| 15 | <sect2>
|
|---|
| 16 | <title>Installation of Coreutils</title>
|
|---|
| 17 |
|
|---|
| 18 | <para>Coreutils has an issue when compiled against Glibc-&glibc-version;.
|
|---|
| 19 | Without the patch below, some of the Coreutils utilities (head, tail, sort etc)
|
|---|
| 20 | will reject their traditional syntax which has been in use for approximately 30
|
|---|
| 21 | years. The old syntax is so pervasive that compatibility must be preserved until
|
|---|
| 22 | the many places where it is used can be updated. More details are provided in
|
|---|
| 23 | the comments inside the patch itself. Use of this patch is by no means
|
|---|
| 24 | compulsory but opting not to use it means you'll have deal with the consequences
|
|---|
| 25 | yourself, i.e. patch the many software packages that use the old syntax. Apply
|
|---|
| 26 | the patch:</para>
|
|---|
| 27 |
|
|---|
| 28 | <screen><userinput>patch -Np1 -i ../&coreutils-posixver-patch;</userinput></screen>
|
|---|
| 29 |
|
|---|
| 30 | <para>Now prepare Coreutils for compilation:</para>
|
|---|
| 31 |
|
|---|
| 32 | <screen><userinput>./configure --prefix=/tools</userinput></screen>
|
|---|
| 33 |
|
|---|
| 34 | <para>Compile the package:</para>
|
|---|
| 35 |
|
|---|
| 36 | <screen><userinput>make</userinput></screen>
|
|---|
| 37 |
|
|---|
| 38 | <para>As discussed earlier, we don't recommend running the test suites for the
|
|---|
| 39 | temporary tools here in this chapter. If you still want to run the Coreutils
|
|---|
| 40 | test suite anyway, the following command will do so:</para>
|
|---|
| 41 |
|
|---|
| 42 | <screen><userinput>make RUN_EXPENSIVE_TESTS=yes check</userinput></screen>
|
|---|
| 43 |
|
|---|
| 44 | <para>The meaning of the make parameter:</para>
|
|---|
| 45 |
|
|---|
| 46 | <itemizedlist>
|
|---|
| 47 | <listitem><para><userinput>RUN_EXPENSIVE_TESTS=yes</userinput>: This tells the
|
|---|
| 48 | test suite to run several additional tests that are considered relatively
|
|---|
| 49 | expensive on some platforms. However, they are generally not a problem on
|
|---|
| 50 | Linux.</para></listitem>
|
|---|
| 51 | </itemizedlist>
|
|---|
| 52 |
|
|---|
| 53 | <para>And install the package:</para>
|
|---|
| 54 |
|
|---|
| 55 | <screen><userinput>make install</userinput></screen>
|
|---|
| 56 |
|
|---|
| 57 | </sect2>
|
|---|
| 58 |
|
|---|
| 59 | <sect2><title> </title><para> </para>
|
|---|
| 60 | <para>The details on this package are found in <xref linkend="contents-coreutils"/>.</para>
|
|---|
| 61 | <para> </para></sect2>
|
|---|
| 62 |
|
|---|
| 63 | </sect1>
|
|---|
| 64 |
|
|---|
