This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: hierarchical projects with configure scripts
- From: Tom Tromey <tom at tromey dot com>
- To: Sergio Durigan Junior <sergiodj at redhat dot com>
- Cc: Tom Tromey <tom at tromey dot com>, Bruno Haible <bruno at clisp dot org>, Paul Eggert <eggert at cs dot ucla dot edu>, bug-gnulib at gnu dot org, gdb-patches at sourceware dot org
- Date: Sat, 01 Sep 2018 00:05:26 -0600
- Subject: Re: hierarchical projects with configure scripts
- References: <87lg8pm4li.fsf@redhat.com> <2805333.pL1CPYTu1R@omega> <87y3cokaai.fsf@redhat.com> <2373646.KA5HVAegPz@omega> <87h8jck0eu.fsf@redhat.com> <87lg8mz2zm.fsf@tromey.com> <875zzqgj09.fsf@redhat.com>
>>>>> "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