From: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
To: Nick Clifton <nickc@redhat.com>,
gcc-patches@gcc.gnu.org, gdb-patches@sourceware.org
Cc: Binutils <binutils@sourceware.org>
Subject: Re: RFC: Changing AC_PROG_CC to AC_PROG_CC_C99 in top level configure
Date: Fri, 30 Apr 2021 14:36:30 -0400 [thread overview]
Message-ID: <8c1b0ed9-e6f3-9c22-45c5-c2680a2a4830@polymtl.ca> (raw)
In-Reply-To: <db8a236e-c195-2494-2442-c64d5655b5b0@redhat.com>
On 2021-04-26 7:32 a.m., Nick Clifton via Gdb-patches wrote:> Hi Guys,
>
> Given that gcc, gdb and now binutils are all now requiring C99 as a
> minimum version of C, are there any objections to updating
> configure.ac to reflect this ?
>
> Cheers
> Nick
>
> diff --git a/configure.ac b/configure.ac
> index a721316d07b..59b4194fb24 100644
> --- a/configure.ac
> +++ b/configure.ac
> @@ -1278,7 +1278,7 @@ else
> WINDMC_FOR_BUILD="\$(WINDMC)"
> fi
>
> -AC_PROG_CC
> +AC_PROG_CC_C99
> AC_PROG_CXX
>
> # We must set the default linker to the linker used by gcc for the correct
Hi Nick,
I think this fix is obvious enough, I encourage you to push it, that
will fix the build failure many people get in opcodes/ppc-dis.c. We'll
just remove the line later when we upgrade to Autoconf 2.71, as simple
as that. For now we use 2.69. If that matters, you have my OK for the
GDB side of things.
Simon
next prev parent reply other threads:[~2021-04-30 18:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-26 11:32 Nick Clifton via Gdb-patches
2021-04-26 19:32 ` Joseph Myers
2021-04-26 20:05 ` Mike Frysinger via Gdb-patches
2021-04-26 21:31 ` Christian Biesinger via Gdb-patches
2021-04-27 10:49 ` Nick Clifton via Gdb-patches
2021-04-27 16:58 ` Joseph Myers
2021-04-30 18:36 ` Simon Marchi via Gdb-patches [this message]
2021-04-30 21:48 ` Jeff Law via Gdb-patches
2021-05-03 6:28 ` Alan Modra via Gdb-patches
2021-05-03 14:47 ` Simon Marchi via Gdb-patches
2021-05-03 16:26 ` Tom Tromey
2021-05-03 21:51 ` Alan Modra via Gdb-patches
2021-05-03 23:30 ` Simon Marchi via Gdb-patches
2021-05-04 12:42 ` Nick Clifton via Gdb-patches
2021-05-04 15:16 ` Simon Marchi via Gdb-patches
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=8c1b0ed9-e6f3-9c22-45c5-c2680a2a4830@polymtl.ca \
--to=gdb-patches@sourceware.org \
--cc=binutils@sourceware.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=nickc@redhat.com \
--cc=simon.marchi@polymtl.ca \
/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