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