public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Alan Modra <amodra@gmail.com>
To: Jeff Law <jeffreyalaw@gmail.com>
Cc: Simon Marchi <simon.marchi@polymtl.ca>,
	Nick Clifton <nickc@redhat.com>,
	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: Mon, 3 May 2021 15:58:26 +0930	[thread overview]
Message-ID: <20210503062825.GG22624@bubble.grove.modra.org> (raw)
In-Reply-To: <15701c5f-5653-f0e4-990a-43094d18a702@gmail.com>

On Fri, Apr 30, 2021 at 03:48:00PM -0600, Jeff Law via Gcc-patches wrote:
> 
> On 4/30/2021 12:36 PM, Simon Marchi via Gcc-patches wrote:
> > 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.
> 
> That works for me.  I'd just sent Alan the trivial patch to make ppc-dis.c
> compile again with C89, but if we're going to update configure.ac
> appropriately, then it wouldn't be needed.

Yes, I prefer the configure fix too.  If we state we require C99 in
binutils then we ought to be able to use C99..

Nick, does the configure.ac change also need to go in all subdirs, to
support people running make in say ld/ rather than running make in the
top build dir?

-- 
Alan Modra
Australia Development Lab, IBM

  reply	other threads:[~2021-05-03  6:28 UTC|newest]

Thread overview: 20+ 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
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 [this message]
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
2021-05-05  0:18       ` Alan Modra
2021-05-05  7:05         ` Iain Sandoe
2021-05-05  7:20           ` Alan Modra
2021-05-05  7:23             ` Iain Sandoe
2021-05-10  8:49             ` Iain Sandoe

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=20210503062825.GG22624@bubble.grove.modra.org \
    --to=amodra@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=jeffreyalaw@gmail.com \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).