On Nov 18 15:06, Biswapriyo Nath via Cygwin wrote:
> Currently the autoconf files in newlib-cygwin repo are in 2.64 version
> but the latest autoconf package is version 2.69. So, autoreconf
> command shows errors. Possible diff attached.
We can update to 2.68, but not 2.69. Newlib still requires older
autotools due to some ancient Cygnus stuff not supported anymore in
Care to fix your patch up and send it in `git format-patch' format to
the newlib AT sourceware DOT org mailing list?
On 2020-11-18 11:19, Biswapriyo Nath via Cygwin wrote:
> I am not familiar with newlib. Please feel free whatever you want to
> do with my previously provided diff. Also my previous question is
Cygwin provides autoconf 2.69 but it's what builds the package that counts, also
perhaps what is available in the cross-build toolchains supported by newlib for
some platforms with limited support.
Some packages or platforms may have maintainers that are not comfortable with or
have difficulty updating their autotools infrastructure, so that part of the
process languishes: some packages are notorious for how old their autotools
Some packages will not build if autoreconfiged, why old releases are still
supported: autoconf/autoheader/autoreconf/autoscan/autoupdate 2.13-2.69,
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada