Re: [PATCH v2 1/1] configure.ac: configurable tooldir install path

[Corinna Vinschen <vinschen@redhat.com>]

On Jan 10 10:03, Mike Frysinger wrote:
> On 10 Jan 2024 10:53, Corinna Vinschen wrote:
> > Maybe we should switch newlib/cygwin to 2.71 as well, eventually?
> > 
> > We're in the process of preparing the next Cygwin release which should
> > be due end of this month.  After that I don't see any reason that we
> > can't bumb the configury to the latest autotools.
> 
> i'm not a fan of diverging from the rest of the source projects.  i want
> the rest of gcc/binutils/gdb move to autoconf-2.71 & automake-1.16, but
> i don't have the cycles to drive that.  i'm also not sure what their
> preference is when it comes to release timings.
> 	autoconf-2.69:   Apr 2012
> 	         2.70:   Dec 2020
> 	         2.71:   Jan 2021
> 	automake-1.15:   Dec 2014
> 	         1.15.1: Jun 2017
> 	         1.16:   Feb 2018
> 	         1.16.5: Oct 2021
> personally i think 2 years is enough for the dev population who actually
> work on these projects, but who knows.
> 
> gcc is currently on autoconf-2.69.  it enforces this:
> config/override.m4:
> 	dnl Ensure exactly this Autoconf version is used
> 	m4_ifndef([_GCC_AUTOCONF_VERSION],
> 	  [m4_define([_GCC_AUTOCONF_VERSION], [2.69])])
> 	dnl Test for the exact version when AC_INIT is expanded.

Right.  We shouldn't switch to 2.71 before gcc/binutils/gdb did.
I thought they already switched, sorry for not checking myself.


Thanks,
Corinna