1 This gives some notes on obtaining the tools required for development.
2 I.E. the tools checked for by the bootstrap script and include:
4 - Autoconf <http://www.gnu.org/software/autoconf/>
5 - Automake <http://www.gnu.org/software/automake/>
6 - Gettext <http://www.gnu.org/software/gettext/>
7 - Git <http://git.or.cz/>
8 - Gperf <http://www.gnu.org/software/gperf/>
9 - Perl <http://www.cpan.org/>
10 - Tar <http://www.gnu.org/software/tar/>
11 - Texinfo <http://www.gnu.org/software/texinfo/>
13 Note please try to install/build official packages for your system.
14 If these are not available then one can make them available only to
15 the coreutils build using the following instructions. Even if the
16 official packages for your system are too old, please install them
17 as they may be required to build the newer versions.
21 # Note Autoconf 2.62 or newer is needed to build automake-1.11
22 git clone --depth=1 git://git.sv.gnu.org/autoconf.git
25 ./configure --prefix=$HOME/coreutils/deps
30 # Note help2man is required to build automake fully
31 git clone git://git.sv.gnu.org/automake.git
33 git checkout -b branch-1.11 --track origin/branch-1.11
35 ./configure --prefix=$HOME/coreutils/deps
38 coreutils uses XZ utils (successor to LZMA) to create
39 a compressed distribution tarball. Using this feature of Automake
40 requires version 1.10a or newer, as well as the xz program itself.
44 git clone git://ctrl.tukaani.org/xz.git
47 ./configure --prefix=$HOME/coreutils/deps
50 Now we can build coreutils as described in README-hacking
51 as long as $PATH starts with $HOME/coreutils/deps/bin, which
52 one can set for the current shell like:
53 $ export PATH=$HOME/coreutils/deps/bin:$PATH