From: Pedro Alves <palves@redhat.com>
To: Simon Marchi <simon.marchi@polymtl.ca>,
Sergio Durigan Junior <sergiodj@redhat.com>
Cc: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
Subject: Re: Breakage on builder Fedora-x86_64-w64-mingw32, revision f99d9b9f436dce02aa06839395c67d400b2a0de0 [gdb-8.1-branch]
Date: Thu, 09 Aug 2018 19:55:00 -0000 [thread overview]
Message-ID: <bf37dc25-4ba1-0b2b-9633-d0766f9f4ea0@redhat.com> (raw)
In-Reply-To: <58670db25a7013cf79b93229a0c80666@polymtl.ca>
On 08/02/2018 10:07 PM, Simon Marchi wrote:
> On 2018-08-02 16:59, Sergio Durigan Junior wrote:
>> On Thursday, August 02 2018, Simon Marchi wrote:
>>
>>> On 2018-08-02 16:37, Sergio Durigan Junior wrote:
>>>> You mean on BuildBot? Unfortunately it's not that easy to execute
>>>> generic commands on the slave with the way things are configure right
>>>> now :-/. What I will do (and was indeed planning to do) is temporarily
>>>> disable e-mail notifications for this builder until we figure out a fix
>>>> for the issue.
>>>
>>> Ah ok, I had hoped you could fit it in one of these steps
>>> (ConfigureGDB or CompileGDB):
>>>
>>> https://git.sergiodj.net/gdb-buildbot.git/tree/master.cfg#n755
>>>
>>> But too bad if it's not possible.
>>
>> It's possible, but not very easy to do that per-builder, which is what
>> you're proposing, right? Unless you think we should do that for every
>> builder, in which case it'd be simpler, indeed.
>
> I think it doesn't hurt to do it on every builder, at worst it's useless. The other builders could suffer from the same problem, in theory, but I suppose they don't because they use the system gettext instead of the included one in intl/. You can "reproduce" the problem in any build by doing "touch $srcdir/intl/plural.y" and "cd $builddir/intl; make plural.o".
I think the easiest is to make this builder configure with --disable-intl.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2018-08-09 19:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-31 20:11 Oh dear. I regret to inform you that commit f99d9b9f436dce02aa06839395c67d400b2a0de0 might be unfortunate [gdb-8.1-branch] gdb-buildbot
2018-07-31 20:11 ` Breakage on builder Fedora-x86_64-w64-mingw32, revision f99d9b9f436dce02aa06839395c67d400b2a0de0 [gdb-8.1-branch] gdb-buildbot
2018-08-02 4:59 ` Sergio Durigan Junior
2018-08-02 12:20 ` Simon Marchi
2018-08-02 20:37 ` Sergio Durigan Junior
2018-08-02 20:52 ` Simon Marchi
2018-08-02 20:59 ` Sergio Durigan Junior
2018-08-02 21:08 ` Simon Marchi
2018-08-09 19:55 ` Pedro Alves [this message]
2018-08-09 20:01 ` Sergio Durigan Junior
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=bf37dc25-4ba1-0b2b-9633-d0766f9f4ea0@redhat.com \
--to=palves@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=sergiodj@redhat.com \
--cc=simon.marchi@polymtl.ca \
/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).