From: Nick Clifton <nickc@redhat.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org, gdb-patches@sourceware.org,
Binutils <binutils@sourceware.org>
Subject: Re: RFC: Changing AC_PROG_CC to AC_PROG_CC_C99 in top level configure
Date: Tue, 27 Apr 2021 11:49:28 +0100 [thread overview]
Message-ID: <68c0bd9b-64a2-a49b-3bb7-c92128e5e625@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2104261928410.641239@digraph.polyomino.org.uk>
Hi Joseph,
> This isn't an objection, since upgrading auto* for the toolchain can be
> complicated, but note that AC_PROG_CC_C99 is obsolete in Autoconf 2.70
Ah - in which case changing to an about-to-be-obsolete macro is probably
a bad idea.
> and instead AC_PROG_CC enables C11 mode if supported. (So moving to the
> latest Autoconf and Automake releases would supersede this change.)
Makes sense. Is changing to autoconf 2.70 something that is planned for
the near future ?
I actually have a Fedora BZ open suggesting that the binutils be
upgraded to use autoconf 2.71. I have put off doing this however as I
am not an autoconf expert and I have no idea what the consequences might be.
Cheers
Nick
next prev parent reply other threads:[~2021-04-27 10:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-26 11:32 Nick Clifton
2021-04-26 19:32 ` Joseph Myers
2021-04-26 20:05 ` Mike Frysinger
2021-04-26 21:31 ` Christian Biesinger
2021-04-27 10:49 ` Nick Clifton [this message]
2021-04-27 16:58 ` Joseph Myers
2021-04-30 18:36 ` Simon Marchi
2021-04-30 21:48 ` Jeff Law
2021-05-03 6:28 ` Alan Modra
2021-05-03 14:47 ` Simon Marchi
2021-05-03 16:26 ` Tom Tromey
2021-05-03 21:51 ` Alan Modra
2021-05-03 23:30 ` Simon Marchi
2021-05-04 12:42 ` Nick Clifton
2021-05-04 15:16 ` Simon Marchi
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=68c0bd9b-64a2-a49b-3bb7-c92128e5e625@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=joseph@codesourcery.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).