From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Jonah Graham <jonah@kichwacoders.com>
Cc: Tom Tromey <tom@tromey.com>,
gdb-patches@sourceware.org, David Edelsohn <dje.gcc@gmail.com>
Subject: Re: Proposal to revert the gnulib update patch
Date: Tue, 04 Sep 2018 18:04:00 -0000 [thread overview]
Message-ID: <87bm9dyw9n.fsf@redhat.com> (raw)
In-Reply-To: <CAPmGMvjskUcL8=piME+_m-vCL4_7A-hHq9pVtNx+vNNAssxdEA@mail.gmail.com> (Jonah Graham's message of "Tue, 4 Sep 2018 07:19:52 +0100")
On Tuesday, September 04 2018, Jonah Graham wrote:
> On Tue, 4 Sep 2018 at 01:46, Sergio Durigan Junior <sergiodj@redhat.com> wrote:
>> I'd like to hear your opinions.
>
> In the short term it would make my life easier. However at some point
> c11 should be allowed for GDB source. If gdb maintainers want to make
> that change now CDT will figure out how to manage.
I absolutely agree we should be moving to more recent standards *and*
compilers. My initial plan is to fix these two gnulib bugs, but I won't
be fully available this week and don't want to cause inconveniences to
other people who are compiling GDB with either an old compiler or on
mingw.
> I have put in a request to Eclipse Infrastructure to get a newer GCC
> on our build machines already:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=538538
Thanks, that is great.
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
next prev parent reply other threads:[~2018-09-04 18:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-29 16:31 Oh dear. I regret to inform you that commit 7a6dbc2fdb2323c35e981f93236f323e9d7c0b24 might be unfortunate gdb-buildbot
2018-08-29 16:31 ` Breakage on builder RHEL-s390x-m64, revision 7a6dbc2fdb2323c35e981f93236f323e9d7c0b24 gdb-buildbot
2018-08-29 16:39 ` Sergio Durigan Junior
2018-08-29 20:42 ` Sergio Durigan Junior
2018-08-29 21:33 ` Tom Tromey
2018-08-29 21:37 ` Sergio Durigan Junior
2018-08-30 0:50 ` Tom Tromey
2018-08-30 3:04 ` Sergio Durigan Junior
2018-09-01 0:01 ` Tom Tromey
2018-09-03 10:04 ` Jonah Graham
2018-09-04 0:46 ` Proposal to revert the gnulib update patch (was: Re: Breakage on builder RHEL-s390x-m64, revision 7a6dbc2fdb2323c35e981f93236f323e9d7c0b24) Sergio Durigan Junior
2018-09-04 6:20 ` Jonah Graham
2018-09-04 18:04 ` Sergio Durigan Junior [this message]
2018-09-04 18:09 ` Proposal to revert the gnulib update patch Tom Tromey
2018-08-30 3:06 ` Breakage on builder RHEL-s390x-m64, revision 7a6dbc2fdb2323c35e981f93236f323e9d7c0b24 Sergio Durigan Junior
2018-08-30 1:55 ` Breakage on builder Debian-s390x-native-extended-gdbserver-m64, " gdb-buildbot
2018-08-30 1:57 ` Breakage on builder Debian-s390x-native-gdbserver-m64, " gdb-buildbot
2018-08-30 1:58 ` Breakage on builder Debian-s390x-m64, " gdb-buildbot
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=87bm9dyw9n.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=dje.gcc@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=jonah@kichwacoders.com \
--cc=tom@tromey.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