public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Jonah Graham <jonah@kichwacoders.com>
Cc: Tom Tromey <tom@tromey.com>,
	 gdb-patches@sourceware.org,  dje.gcc@gmail.com
Subject: Proposal to revert the gnulib update patch (was: Re: Breakage on builder RHEL-s390x-m64, revision 7a6dbc2fdb2323c35e981f93236f323e9d7c0b24)
Date: Tue, 04 Sep 2018 00:46:00 -0000	[thread overview]
Message-ID: <87y3ciytr7.fsf_-_@redhat.com> (raw)
In-Reply-To: <CAPmGMvg9JUcO1JmV53W9iLFywGMC0=9AOOzLTXcLZ==gBoMKNQ@mail.gmail.com>	(Jonah Graham's message of "Mon, 3 Sep 2018 11:04:10 +0100")

On Monday, September 03 2018, Jonah Graham wrote:

>> b) Is there a "stddef.h" file in the build dir?  Does it declare
>> "max_align_t"?  This is causing the "unknown type name ‘max_align_t’"
>> error.
>
> Our daily build (for Eclipse CDT testing) of GDB's master has started
> failing because of this issue too:
> https://ci.eclipse.org/cdt/job/debug-tests-master-gdb-master/1666/console

Thanks, Jonah.

I'm thinking about reverting the gnulib update patch.  I'm on PTO this
week (in theory :-/), and not sure if I'll be able to address these
issues in a timely manner.  Aside from this c11 issue, there's also the
mingw compilation failure.

Since the main reason for updating gnulib was to fix PR gdb/23558, as a
workaround, I propose that we backport just the upstream gnulib patch
that fixes the problem:

a96d2e67052c879b1bcc5bc461722beac75fc372

I'd like to hear your opinions.

Thanks,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/

  reply	other threads:[~2018-09-04  0:46 UTC|newest]

Thread overview: 19+ 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                   ` Sergio Durigan Junior [this message]
2018-09-04  6:20                     ` Proposal to revert the gnulib update patch (was: Re: Breakage on builder RHEL-s390x-m64, revision 7a6dbc2fdb2323c35e981f93236f323e9d7c0b24) Jonah Graham
2018-09-04 18:04                       ` Proposal to revert the gnulib update patch Sergio Durigan Junior
2018-09-04 18:09                     ` 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
2018-09-04 17:02 Proposal to revert the gnulib update patch (was: Re: Breakage on builder RHEL-s390x-m64, revision 7a6dbc2fdb2323c35e981f93236f323e9d7c0b24) Kyrill Tkachov

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=87y3ciytr7.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).