Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@polymtl.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org, Pedro Alves <palves@redhat.com>
Subject: Re: MinGW build failure for GDB 8.2.90 with source-highlight
Date: Tue, 12 Mar 2019 02:31:00 -0000	[thread overview]
Message-ID: <ed82342fcc7e52f9ef3d3031aa69e793@polymtl.ca> (raw)
In-Reply-To: <83ef7d5wak.fsf@gnu.org>

On 2019-03-11 10:18, Eli Zaretskii wrote:
> Ping!  This discussion seems to have stalled.  I'd like to have it
> solved before GDB 8.3 is released.

Agreed, this is definitely a blocker for the release.  I recorded it 
here:

https://www.sourceware.org/gdb/wiki/GDB_8.3_Release

> 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

If the change is localized in one or a handful of files, I think it 
would be acceptable for the 8.3 release, since the alternative solution 
would be (1) a lot of work and (2) risky.

Can you post a patch that fixes the build for you?

Pedro, did you have a branch where you put all of gdb in the gdb 
namespace?  I only found this branch, but it's using the gnulib:: 
namespace, which is not the same.

https://github.com/palves/gdb/commits/palves/cxx-gnulib-namespace

I just started to try to do it to get a feel of what's needed.  I guess 
we need to put pretty much everything except includes (and maybe some 
other rare exceptions) between namespace gdb { ... }?  And of course 
define GNULIB_NAMESPACE to gdb.

Simon


  reply	other threads:[~2019-03-12  2:31 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
2019-03-12  2:31   ` Simon Marchi [this message]
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=ed82342fcc7e52f9ef3d3031aa69e793@polymtl.ca \
    --to=simon.marchi@polymtl.ca \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@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