From: Mike Frysinger <vapier@gentoo.org>
To: newlib@sourceware.org, "Frager, Neal" <neal.frager@amd.com>,
"jjohnstn@redhat.com" <jjohnstn@redhat.com>,
"thomas.petazzoni@bootlin.com" <thomas.petazzoni@bootlin.com>,
"cjwfirmware@vxmdesign.com" <cjwfirmware@vxmdesign.com>
Subject: Re: [PATCH v2 1/1] configure.ac: configurable tooldir install path
Date: Wed, 10 Jan 2024 15:44:44 -0500 [thread overview]
Message-ID: <ZZ8BvKTb8JkdxAr1@vapier> (raw)
In-Reply-To: <ZZ7EHebQivv37iBx@calimero.vinschen.de>
[-- Attachment #1: Type: text/plain, Size: 1641 bytes --]
On 10 Jan 2024 17:21, Corinna Vinschen wrote:
> 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.
if gcc switches, then yeah, we def should switch newlib, and that part i
could help with if no one else gets to it first.
-mike
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2024-01-10 20:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-09 10:39 Neal Frager
2024-01-09 14:18 ` Frager, Neal
2024-01-09 15:35 ` Frager, Neal
2024-01-10 9:53 ` Corinna Vinschen
2024-01-10 15:03 ` Mike Frysinger
2024-01-10 16:21 ` Corinna Vinschen
2024-01-10 20:44 ` Mike Frysinger [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZZ8BvKTb8JkdxAr1@vapier \
--to=vapier@gentoo.org \
--cc=cjwfirmware@vxmdesign.com \
--cc=jjohnstn@redhat.com \
--cc=neal.frager@amd.com \
--cc=newlib@sourceware.org \
--cc=thomas.petazzoni@bootlin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).