Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: gdb-patches@sourceware.org
Subject: Re: MinGW build failure for GDB 8.2.90 with source-highlight
Date: Mon, 11 Mar 2019 14:18:00 -0000	[thread overview]
Message-ID: <83ef7d5wak.fsf@gnu.org> (raw)
In-Reply-To: <83r2bibvlv.fsf@gnu.org> (message from Eli Zaretskii on Thu, 07	Mar 2019 16:35:40 +0200)

Ping!  This discussion seems to have stalled.  I'd like to have it
solved before GDB 8.3 is released.

If no better ideas come up, I'd like to commit the change described
here:

> Perhaps we should simply #undef these two symbols before including
> <fstream>?

TIA


  parent reply	other threads:[~2019-03-11 14:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-07 14:36 Eli Zaretskii
2019-03-07 16:59 ` Simon Marchi
2019-03-07 17:11   ` Pedro Alves
2019-03-07 18:09     ` Simon Marchi
2019-03-07 18:20       ` Pedro Alves
2019-03-07 18:24         ` Simon Marchi
2019-03-07 20:29         ` Eli Zaretskii
2019-03-07 20:13   ` Eli Zaretskii
2019-03-11 14:18 ` Eli Zaretskii [this message]
2019-03-12  2:31   ` Simon Marchi
2019-03-12 10:52     ` Pedro Alves
2019-03-12 13:43       ` Simon Marchi
2019-03-12 15:49     ` Eli Zaretskii
2019-03-12 16:29       ` Simon Marchi
2019-03-12 17:53         ` Eli Zaretskii

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=83ef7d5wak.fsf@gnu.org \
    --to=eliz@gnu.org \
    --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