From: Tom Tromey <tom@tromey.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: Tom Tromey <tom@tromey.com>, Bruno Haible <bruno@clisp.org>,
Paul Eggert <eggert@cs.ucla.edu>,
bug-gnulib@gnu.org, gdb-patches@sourceware.org
Subject: Re: hierarchical projects with configure scripts
Date: Sat, 01 Sep 2018 06:05:00 -0000 [thread overview]
Message-ID: <874lf9sqft.fsf@tromey.com> (raw)
In-Reply-To: <875zzqgj09.fsf@redhat.com> (Sergio Durigan Junior's message of "Fri, 31 Aug 2018 20:26:46 -0400")
>>>>> "Sergio" == Sergio Durigan Junior <sergiodj@redhat.com> writes:
> Another possibility that may be simpler for GDB, is to change its
> configure.ac files to require C99 or later everywhere. At this point
> it's more trouble than it's worth to tweak source code or makefiles to
> cater to compilers operating in C89 mode. Just tell your C compiler to
> support C99-or-better everywhere, and your life will surely be
> simpler.
Sergio> I don't know if just requiring C99 or later would be enough to solve
Sergio> this problem, but it's something to consider for GDB, I think.
I personally think it would be fine -- C99 is nearly 20 years old now,
surely we can afford to upgrade -- but I think this would have to be run
by the binutils list as well.
Also there's the question of how it would be implemented. Like, if it
relied on modifying CFLAGS, then that would still interfere how this is
supposed to be a user-controlled variable.
Tom
next prev parent reply other threads:[~2018-09-01 6:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87lg8pm4li.fsf@redhat.com>
[not found] ` <2805333.pL1CPYTu1R@omega>
[not found] ` <87y3cokaai.fsf@redhat.com>
[not found] ` <2373646.KA5HVAegPz@omega>
2018-08-30 3:18 ` Sergio Durigan Junior
2018-08-31 20:38 ` Tom Tromey
2018-09-01 0:26 ` Sergio Durigan Junior
2018-09-01 6:05 ` Tom Tromey [this message]
2018-09-01 6:59 ` Eli Zaretskii
2018-09-01 7:42 ` Paul Eggert
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=874lf9sqft.fsf@tromey.com \
--to=tom@tromey.com \
--cc=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=gdb-patches@sourceware.org \
--cc=sergiodj@redhat.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).