From: Sergio Durigan Junior <sergiodj@redhat.com>
To: gdb-patches@sourceware.org
Cc: David Edelsohn <dje.gcc@gmail.com>
Subject: Re: Breakage on builder RHEL-s390x-m64, revision 7a6dbc2fdb2323c35e981f93236f323e9d7c0b24
Date: Thu, 30 Aug 2018 03:06:00 -0000 [thread overview]
Message-ID: <87lg8ok0yv.fsf@redhat.com> (raw)
In-Reply-To: <87a7p4lx9u.fsf@redhat.com> (Sergio Durigan Junior's message of "Wed, 29 Aug 2018 16:42:53 -0400")
On Wednesday, August 29 2018, I wrote:
> On Wednesday, August 29 2018, I wrote:
>
>> On Wednesday, August 29 2018, gdb-buildbot wrote:
>>
>>> Unfortunately it seems that there is a breakage on GDB.
>>>
>>> Commit title: 'Update gnulib to current upstream master'
>>> Revision: 7a6dbc2fdb2323c35e981f93236f323e9d7c0b24
>>
>> I'm investigating this.
>
> Hello, David,
>
> After my last commit, which updated GDB's local copy of gnulib, I'm
> seeing a breakage on the RHEL 7.1 s390x builder (see the rest of the
> quoted message). Unfortunately I don't have easy access to a similar
> machine, so I would like to know if:
>
> 1) You could help me with investigating this a bit more, or
>
> 2) You could grant me temporary access to the machine so I can
> investigate the problem.
>
> I would like to know a few things:
>
> a) Why is GCC apparently not using the C99 mode when compiling gnulib.
> This is causing the "‘for’ loop initial declarations are only allowed in
> C99 mode" error.
>
> 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.
>
> Thanks in advance,
Hi again, David,
As it turns out, I managed to reproduce the problem locally here, so
there's no need for the temporary access anymore.
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/
next prev parent reply other threads:[~2018-08-30 3:06 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 ` Proposal to revert the gnulib update patch Sergio Durigan Junior
2018-09-04 18:09 ` Tom Tromey
2018-08-30 3:06 ` Sergio Durigan Junior [this message]
2018-08-30 1:55 ` Breakage on builder Debian-s390x-native-extended-gdbserver-m64, revision 7a6dbc2fdb2323c35e981f93236f323e9d7c0b24 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=87lg8ok0yv.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=dje.gcc@gmail.com \
--cc=gdb-patches@sourceware.org \
/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