Matej Cepl wrote: > Eric Blake, Wed, 03 Jun 2009 06:58:02 -0700: > >>>> I'll update the automake info... >>> I just pushed this: >>> http://git.savannah.gnu.org/gitweb/?p=coreutils.git;a=commit;h=ba6e08c >> That's still misleading. Automake 1.11 is a stable release, and distros >> are starting to pick it up as such. At present, it is no longer >> necessary to check out automake.git to build coreutils. > > I would stress "starting to" in your response: > > bradford:~$ cat /etc/fedora-release > Fedora release 11 (Leonidas) > bradford:~$ rpm -q automake > automake-1.10.2-3.noarch > bradford:~$ > > This is not-yet-released Fedora 11, which is distro known to distribute > always obsolete versions of packages.
automake-1.11 just went into Fedora 11 which started an interesting discussion :) https://www.redhat.com/archives/fedora-devel-list/2009-June/msg02451.html Anyway I've updated the development prerequisites doc to be more general in the attached patch. cheers, Pádraig.
>From d9caf56b80eb1d65686eba8c185de739a05edd42 Mon Sep 17 00:00:00 2001 From: =?utf-8?q?P=C3=A1draig=20Brady?= <[email protected]> Date: Mon, 22 Jun 2009 09:51:34 +0100 Subject: [PATCH] maint: generalize the development prerequisites doc * README-prereq: Remove the Fedora 8 specific information and generalize the information to be applicable to any system. --- README-prereq | 79 +++++++++++++++++++++++++++++++-------------------------- 1 files changed, 43 insertions(+), 36 deletions(-) diff --git a/README-prereq b/README-prereq index f050410..eb640a9 100644 --- a/README-prereq +++ b/README-prereq @@ -1,36 +1,43 @@ -Detailed below are concrete examples for -getting the prerequisites for particular systems. - -- GNU/Linux - fedora - - This shows the steps for getting the tools required to build coreutils - on a Fedora 8 system. We try to use official packages where possible. - The three methods described for making these required packages available - should help clarify build requirements on GNU/Linux systems. - - 1. Make sure the official distro git package is installed: - # yum install git - - 2. The distro autoconf is too old, but there is a newer one available - so we rebuild that and make it available to the full system: - # yum install emacs #autoconf build requires emacs (20MB) - # rpmbuild --rebuild http://download.fedora.redhat.com/pub/fedora/linux/development/source/SRPMS/autoconf-2.63-1.fc10.src.rpm - # rpm -Uvh /usr/src/redhat/RPMS/noarch/autoconf-2.63-1.fc8.noarch.rpm - Note Autoconf 2.62 or newer is needed to build automake-1.11 in step 3. - Apply the same method to build and install "xz". - - 3. The latest stable automake (1.10.1) was not new enough, so we download - and build automake-1.11 or newer from its repository and make it available - just to coreutils: - # yum install help2man #required to build automake fully - $ git clone git://git.sv.gnu.org/automake.git - $ cd automake - $ git checkout -b branch-1.11 --track origin/branch-1.11 - $ ./bootstrap - $ ./configure --prefix=$HOME/coreutils/deps - $ make install - - Now we can build coreutils as described in README-hacking - as long as $PATH starts with $HOME/coreutils/deps/bin, which - one can set for the current shell like: - $ export PATH=$HOME/coreutils/deps/bin:$PATH +This describes how to obtain the packages required for development. +I.E. the packages listed in the buildreq variable in bootstrap.conf +and checked for at build time by the bootstrap script. +Note the requirements to build the released archive are much less +and are just the requirements of the standard ./configure && make procedure. + +Note please try to install/build official packages for your system. +If these are not available then one can make them available only to +coreutils, using the following instructions. Even if the official +packages for your system are too old, please install them as they may +be required to build the newer versions. + +* autoconf * + + # Note Autoconf 2.62 or newer is needed to build automake-1.11 + git clone --depth=1 git://git.sv.gnu.org/autoconf.git + git checkout v2.62 + autoreconf -vi + ./configure --prefix=$HOME/coreutils/deps + make install + +* automake * + + # Note help2man is required to build automake fully + git clone git://git.sv.gnu.org/automake.git + cd automake + git checkout -b branch-1.11 --track origin/branch-1.11 + ./bootstrap + ./configure --prefix=$HOME/coreutils/deps + make install + +* xz * + + git clone git://ctrl.tukaani.org/xz.git + cd xz + ./autogen.sh + ./configure --prefix=$HOME/coreutils/deps + make install + +Now we can build coreutils as described in README-hacking +as long as $PATH starts with $HOME/coreutils/deps/bin, which +one can set for the current shell like: + $ export PATH=$HOME/coreutils/deps/bin:$PATH -- 1.6.2.5
_______________________________________________ Bug-coreutils mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-coreutils
