From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: GDB 9.1 release 2019-12-23 update
Date: Tue, 24 Dec 2019 16:21:00 -0000 [thread overview]
Message-ID: <831rstwv8g.fsf@gnu.org> (raw)
In-Reply-To: <20191224034652.GA25918@adacore.com> (message from Joel Brobecker on Tue, 24 Dec 2019 07:46:52 +0400)
> Date: Tue, 24 Dec 2019 07:46:52 +0400
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: gdb-patches@sourceware.org
>
> > > - [Eliz] libtcf fails to build on MinGW
> > > https://sourceware.org/bugzilla/show_bug.cgi?id=25155
> > >
> > > Problem reported to binutils on Dec 17th, but so far
> > > no answer as far as I can tell.
> > > https://sourceware.org/ml/binutils/2019-12/msg00277.html
> > >
> > > If we don't get an answer after the end of year holidays,
> > > I suggest we send in a patch, which will likely help move
> > > things along. From Eli's message on bugzilla, we shouldn't
> > > be far from having one.
> >
> > I already have a patch, so I can apply it whenever you say so.
>
> Let's try to have it reviewed by the binutils folks if we can.
> It seems relatively straightforward, but I tend to avoid fixing
> things in a branch before it gets fixed in master. Maybe send
> the patch to binutils with an RFA? If that doesn't work, then
> we'll consider the option of just patching our branch so
> we can release.
I added an attachment with the patch to the Bugzilla report, it should
appear shortly on the bug-binutils mailing list. Let's see what
happens next.
next prev parent reply other threads:[~2019-12-24 16:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-23 9:30 Joel Brobecker
2019-12-23 14:14 ` Eli Zaretskii
2019-12-23 14:32 ` Eli Zaretskii
2019-12-24 3:47 ` Joel Brobecker
2019-12-24 12:24 ` Andrew Burgess
2019-12-24 15:52 ` Eli Zaretskii
2020-01-03 16:21 ` Tom Tromey
2019-12-24 16:21 ` Eli Zaretskii [this message]
2019-12-26 22:40 ` Christian Biesinger via gdb-patches
2019-12-27 7:49 ` Eli Zaretskii
2019-12-25 21:36 ` Andrew Burgess
2020-01-02 10:56 ` Joel Brobecker
2020-01-06 22:00 ` Andrew Burgess
2019-12-28 16:22 ` Hannes Domani via gdb-patches
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=831rstwv8g.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).