Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Nick Alcock <nick.alcock@oracle.com>
Cc: brobecker@adacore.com, gdb-patches@sourceware.org
Subject: Re: libctf compilation failure on MinGW
Date: Sat, 04 Jul 2020 21:19:16 +0300	[thread overview]
Message-ID: <83sge7ta6z.fsf@gnu.org> (raw)
In-Reply-To: <878sfztabt.fsf@esperi.org.uk> (message from Nick Alcock on Sat,  04 Jul 2020 19:16:22 +0100)

> From: Nick Alcock <nick.alcock@oracle.com>
> Cc: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
> Date: Sat, 04 Jul 2020 19:16:22 +0100
> 
> > GDB is about to branch for the imminent GDB 10.1 release, and
> > currently the problems I described back then are still with us.
> 
> Oh, I thought you pushed a fix already! Sorry!

We did, but only on the-then GDB 9.1 branch.  The master branch wasn't
changed, as we expected to have you update the upstream with the
proper solution.

> I'll post a fix sticking suitable E* #defines in once I get back from
> holiday on Tuesday.
> 
> > we'd like a solution soon, and need to decide whether to go with the
> > same workaround we used for GDB 9.1 or use a better change from you.
> 
> I think that workaround is in hindsight better than the change I
> proposed, and should go in trunk. :/

Thanks.


  reply	other threads:[~2020-07-04 18:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-02 13:45 Eli Zaretskii
2020-07-04 18:16 ` Nick Alcock
2020-07-04 18:19   ` Eli Zaretskii [this message]
2020-07-18 19:06   ` Joel Brobecker

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=83sge7ta6z.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=nick.alcock@oracle.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