source: chapter05/coreutils.xml@ f4c628c

<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
  <!ENTITY % general-entities SYSTEM "../general.ent">
  %general-entities;
]>

<sect1 id="ch-tools-coreutils" role="wrap">
  <?dbhtml filename="coreutils.html"?>

  <title>Coreutils-&coreutils-version;</title>

  <indexterm zone="ch-tools-coreutils">
    <primary sortas="a-Coreutils">Coreutils</primary>
    <secondary>tools</secondary>
  </indexterm>

  <sect2 role="package">
    <title/>

    <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
    href="../chapter06/coreutils.xml"
    xpointer="xpointer(/sect1/sect2[1]/para[1])"/>

    <segmentedlist>
      <segtitle>&buildtime;</segtitle>
      <segtitle>&diskspace;</segtitle>

      <seglistitem>
        <seg>&coreutils-ch5-sbu;</seg>
        <seg>&coreutils-ch5-du;</seg>
      </seglistitem>
    </segmentedlist>

  </sect2>

  <sect2 role="installation">
    <title>Installation of Coreutils</title>

    <para>Prepare Coreutils for compilation:</para>

<screen><userinput>./configure --prefix=/tools</userinput></screen>

    <para>Compile the package:</para>

<screen><userinput>make</userinput></screen>

    <para>To test the results, issue:
    <userinput>make RUN_EXPENSIVE_TESTS=yes check</userinput>. The
    <parameter>RUN_EXPENSIVE_TESTS=yes</parameter> parameter tells the
    test suite to run several additional tests that are considered
    relatively expensive (in terms of CPU power and memory usage) on some
    platforms, but generally are not a problem on Linux.</para>

    <para>Install the package:</para>

<screen><userinput>make install</userinput></screen>

    <para>The above command refuses to install <filename>su</filename>
    because it cannot install it setuid root as a non-privileged user. By
    manually installing it with a different name, we can use it for running
    tests in the final system as a non-privileged user and we keep a possibly
    useful <command>su</command> from our host first place in our PATH. Install
    it with:</para>

<screen><userinput>cp -v src/su /tools/bin/su-tools</userinput></screen>

  </sect2>

  <sect2 role="content">
    <title/>

    <para>Details on this package are located in
    <xref linkend="contents-coreutils" role="."/></para>

  </sect2>

</sect1>