FYI: bump needed auto* versions

[Tom Tromey]

Ralf Wildenhues (CCd) went through the whole toolchain (gcc, binutils,
gdb, etc) and bumped the required auto* versions to the latest stable
releases.

This seems to be a good idea generally, so I think we ought to do it for
Classpath as well.

The only actual source change needed for this is to update
cp-hacking.texinfo.  You might think that, given this, perhaps we should
not update the versions -- but I think it still makes sense, in that it
means that future patches can now rely on these minimums.

Tom

2009-08-15  Ralf Wildenhues  <Ralf.Wildenhues@...>

        * doc/cp-hacking.texinfo (Needed Tools and Libraries): Bump
        Autoconf version to 2.64, Automake to 1.11, M4 to 1.4.6.

Index: doc/cp-hacking.texinfo
===================================================================
RCS file: /cvsroot/classpath/classpath/doc/cp-hacking.texinfo,v
retrieving revision 1.7
diff -u -r1.7 cp-hacking.texinfo
--- doc/cp-hacking.texinfo 9 Mar 2008 16:28:58 -0000 1.7
+++ doc/cp-hacking.texinfo 17 Aug 2009 16:08:11 -0000
@@ -11,7 +11,7 @@
 This file contains important information you will need to know if you
 are going to hack on the GNU Classpath project code.
 
-Copyright (C) 1998,1999,2000,2001,2002,2003,2004,2005,2007 Free Software Foundation, Inc.
+Copyright (C) 1998,1999,2000,2001,2002,2003,2004,2005,2007,2009 Free Software Foundation, Inc.
 
 @ifnotplaintext
 @dircategory GNU Libraries
@@ -351,13 +351,13 @@
 @item
 CVS 1.11+
 @item
-automake 1.9+
+automake 1.11+
 @item
-autoconf 2.59+
+autoconf 2.64+
 @item
 libtool 1.5+
 @item
-GNU m4 1.4
+GNU m4 1.4.6
 @item
 texinfo 4.2+
 @end itemize

[gnu_andrew]

2009/8/17 Tom Tromey <tromey@...>:

> Ralf Wildenhues (CCd) went through the whole toolchain (gcc, binutils,
> gdb, etc) and bumped the required auto* versions to the latest stable
> releases.
>
> This seems to be a good idea generally, so I think we ought to do it for
> Classpath as well.
>
> The only actual source change needed for this is to update
> cp-hacking.texinfo.  You might think that, given this, perhaps we should
> not update the versions -- but I think it still makes sense, in that it
> means that future patches can now rely on these minimums.
>

The autoconf jump seems a bit steep.  2.64 was only released at the
end of July, less than a month ago.

> Tom
>
> 2009-08-15  Ralf Wildenhues  <Ralf.Wildenhues@...>
>
>        * doc/cp-hacking.texinfo (Needed Tools and Libraries): Bump
>        Autoconf version to 2.64, Automake to 1.11, M4 to 1.4.6.
>
> Index: doc/cp-hacking.texinfo
> ===================================================================
> RCS file: /cvsroot/classpath/classpath/doc/cp-hacking.texinfo,v
> retrieving revision 1.7
> diff -u -r1.7 cp-hacking.texinfo
> --- doc/cp-hacking.texinfo      9 Mar 2008 16:28:58 -0000       1.7
> +++ doc/cp-hacking.texinfo      17 Aug 2009 16:08:11 -0000
> @@ -11,7 +11,7 @@
>  This file contains important information you will need to know if you
>  are going to hack on the GNU Classpath project code.
>
> -Copyright (C) 1998,1999,2000,2001,2002,2003,2004,2005,2007 Free Software Foundation, Inc.
> +Copyright (C) 1998,1999,2000,2001,2002,2003,2004,2005,2007,2009 Free Software Foundation, Inc.
>
>  @ifnotplaintext
>  @dircategory GNU Libraries
> @@ -351,13 +351,13 @@
>  @item
>  CVS 1.11+
>  @item
> -automake 1.9+
> +automake 1.11+
>  @item
> -autoconf 2.59+
> +autoconf 2.64+
>  @item
>  libtool 1.5+
>  @item
> -GNU m4 1.4
> +GNU m4 1.4.6
>  @item
>  texinfo 4.2+
>  @end itemize
>
>

--
Andrew :-)

Free Java Software Engineer
Red Hat, Inc. (http://www.redhat.com)

Support Free Java!
Contribute to GNU Classpath and the OpenJDK
http://www.gnu.org/software/classpath
http://openjdk.java.net

PGP Key: 94EFD9D8 (http://subkeys.pgp.net)
Fingerprint: F8EF F1EA 401E 2E60 15FA  7927 142C 2591 94EF D9D8

[Ralf Wildenhues]

Hello,

* Tom Tromey wrote on Mon, Aug 17, 2009 at 06:09:14PM CEST:
> Ralf Wildenhues (CCd) went through the whole toolchain (gcc, binutils,
> gdb, etc) and bumped the required auto* versions to the latest stable
> releases.

I didn't actually commit it *yet*.  I merely posted the patches to do
so.  There is at least one regression in Autoconf 2.64 we still need to
take care of, however:
<http://thread.gmane.org/gmane.comp.gnu.binutils/42947/focus=42968>
which we will fix with a patch to config/override.m4 in the GCC tree.

> 2009-08-15  Ralf Wildenhues  <Ralf.Wildenhues@...>
>
> * doc/cp-hacking.texinfo (Needed Tools and Libraries): Bump
> Autoconf version to 2.64, Automake to 1.11, M4 to 1.4.6.

Thanks for taking care of this.

Cheers,
Ralf

[Tom Tromey]

>>>>> "Andrew" == Andrew John Hughes <gnu_andrew@...> writes:

Andrew> The autoconf jump seems a bit steep.  2.64 was only released at the
Andrew> end of July, less than a month ago.

I guess you can downgrade it if you feel strongly about it.
It is true that this is really "bleed-in" from GCC.  I do think it is a
reasonable choice (I would not have committed it otherwise), but there
may be other reasonable choices.

Tom

[Mark Wielaard]

Hi Tom,

On Mon, 2009-08-17 at 10:09 -0600, Tom Tromey wrote:
> The only actual source change needed for this is to update
> cp-hacking.texinfo.  You might think that, given this, perhaps we should
> not update the versions -- but I think it still makes sense, in that it
> means that future patches can now rely on these minimums.

There is also autogen.sh (since we don't checkin the generated files).
You will need something like this to accept later libtool versions:

diff -u -r1.20 autogen.sh
--- autogen.sh 18 May 2007 20:18:53 -0000 1.20
+++ autogen.sh 17 Aug 2009 21:28:19 -0000
@@ -18,7 +18,7 @@
 if ${LIBTOOLIZE} --version < /dev/null > /dev/null 2>&1 ; then
  libtool_version=`${LIBTOOLIZE} --version | sed 's/^.*[^0-9.]\([0-9]\{1,\}\.[0-9.]\{1,\}\).*/\1/'`
  case $libtool_version in
-    1.5*)
+    1.5* | 2.[0-9]*)
  have_libtool=true
  ;;
  esac

The rest is fine I think, using a lower version isn't really fatal (is it?)

Cheers,

Mark

[Ralf Wildenhues]

* Mark Wielaard wrote on Mon, Aug 17, 2009 at 11:30:15PM CEST:
>
> There is also autogen.sh (since we don't checkin the generated files).
> You will need something like this to accept later libtool versions:

> --- autogen.sh 18 May 2007 20:18:53 -0000 1.20
> +++ autogen.sh 17 Aug 2009 21:28:19 -0000
> @@ -18,7 +18,7 @@
>  if ${LIBTOOLIZE} --version < /dev/null > /dev/null 2>&1 ; then
>   libtool_version=`${LIBTOOLIZE} --version | sed 's/^.*[^0-9.]\([0-9]\{1,\}\.[0-9.]\{1,\}\).*/\1/'`
>   case $libtool_version in
> -    1.5*)
> +    1.5* | 2.[0-9]*)
>   have_libtool=true
>   ;;
>   esac
>
> The rest is fine I think, using a lower version isn't really fatal (is it?)

It should work fine to use newer Autoconf and Automake with older
Libtool versions, yes.

Cheers,
Ralf