Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@polymtl.ca>
To: 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, 02 Aug 2018 12:20:00 -0000	[thread overview]
Message-ID: <206639a56eca9fe5aa2a64629f200724@polymtl.ca> (raw)
In-Reply-To: <87lg9pbby7.fsf@redhat.com>

On 2018-08-02 00:59, Sergio Durigan Junior wrote:
> On Tuesday, July 31 2018, gdb-buildbot wrote:
> 
>> Unfortunately it seems that there is a breakage on GDB.
>> 
>> Commit title: 'Set GDB version number to 8.1.1.'
>> Revision: f99d9b9f436dce02aa06839395c67d400b2a0de0
> 
> FWIW, this is still the same issue discussed here:
> 
> https://sourceware.org/ml/gdb-patches/2018-07/msg00626.html

As a hacky workaround, maybe the build commands could include touching 
src/intl/plural.c?

Simon


  reply	other threads:[~2018-08-02 12:20 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 [this message]
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
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=206639a56eca9fe5aa2a64629f200724@polymtl.ca \
    --to=simon.marchi@polymtl.ca \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=sergiodj@redhat.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