coreutils.xml 2.4 KB

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