%general-entities; ]> coreutils &coreutils-version;
&coreutils-url;
Coreutils-&coreutils-version; Coreutils tools <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 There's an internal issue with Coreutils which makes some of the programs behave abnormally if you build using an older kernel. Apply a patch to fix the issue: patch -Np1 -i ../&coreutils-old-kernel-patch; Prepare Coreutils for compilation: ./configure --prefix=/tools --enable-install-program=hostname The meaning of the configure options: --enable-install-program=hostname This enables the hostname binary to be built and installed – it is disabled by default but is required by the Perl test suite. Compile the package: make Compilation is now complete. As discussed earlier, running the test suite is not mandatory for the temporary tools here in this chapter. To run the Coreutils test suite anyway, issue the following command: make RUN_EXPENSIVE_TESTS=yes check The RUN_EXPENSIVE_TESTS=yes 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. Install the package: make install The above command refuses to install su because the program cannot be installed 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 su from our host first in our PATH. Install it with: cp -v src/su /tools/bin/su-tools <para>Details on this package are located in <xref linkend="contents-coreutils" role="."/></para> </sect2> </sect1>