Re: newlib: require autoconf-2.69

On Jan  5 20:46, Mike Frysinger wrote:
> On 05 Jan 2022 13:10, Corinna Vinschen wrote:
> > On Dec 30 13:39, Mike Frysinger wrote:
> > > The top-level newlib dir is already using autoconf-2.69, and all the
> > > subdirs are using autoconf-2.68.  Update them all to use 2.69 as a
> > > prereq and then regenerate them accordingly.
> > > 
> > > The README file already says to use autoconf-2.69.
> > 
> > Yeah, but...
> > 
> > The AC_PREREQ only checks for the minimum required autoconf version for
> > *this* specific autoconf file.  AC_PREREQ([2.52]) doesn't mean we have to
> > use 2.52, but any later version will suffice.  All current autoconf
> > files are compatible with 2.69.  Neither binutils-gdb, nor gcc changed
> > their files to require 2.69.  So it's note quite clear to me what this
> > patch accomplishes.
> 
> that's incorrect.  gcc & binutils-gdb have config/override.m4 which requires
> autoconf-2.69 exactly is used.  no older versions, no newer versions, only
> 2.69 is permitted.

You're right, but that's not what I was up to.  Requiring 2.69 doesn't
mean we have to (or even should) change AC_PREREQ in every single file.
But, anyway, it probably won't hurt either, so just go ahead.

> > Autoconf 2.71 is the next version introducing backward incompatibilities.
> > Wouldn't it make more sense to fix up the incompatibilities (if any)
> > and update the affected files to 2.71 to be more future-proof?
> 
> since newlib keeps its top-level files & config/ files in sync with the
> binutils-gdb & gcc repos, i don't think moving to a version diff from them
> is a good idea.  unless you want to completely throw away all of the top
> level files and have newlib/libgloss go their own completely independent
> route.
> -mike

Ok.


Thanks,
Corinna