mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: libstdc++ namespace pollution
Date: Tue, 3 Jan 2017 13:29:08 -0500	[thread overview]
Message-ID: <20170103182908.GH1555@brightrain.aerifal.cx> (raw)
In-Reply-To: <CAK4o1WyWrmszFFqO1u=EWSnX-C5xgt2-ZJDhjWwr1oOTKGbpzg@mail.gmail.com>

On Tue, Jan 03, 2017 at 05:44:47PM +0000, Justin Cormack wrote:
> I have been trying to build a C++ program recently, and came across
> the issue that
> 
> 1. libstdc++ always defines _GNU_SOURCE see
> https://gcc.gnu.org/onlinedocs/libstdc++/faq.html#faq.predefined
> 2. Musl defines pretty much everything once _GNU_SOURCE is defined

So does glibc. :)

> In this case the issue was that the program included <signal.h> and
> then the register names REG_RIP etc were #defined as numeric
> constants, while the program wanted to use them as names for an enum.
> 
> Does anyone have any recommendations (wondering about trying clang
> libc++ perhaps)?

This is a known issue that the gcc people want to fix, I think. It
might be possible to patch it out already it you're prepared to track
down things that break and fix them.

Rich


  reply	other threads:[~2017-01-03 18:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-03 17:44 Justin Cormack
2017-01-03 18:29 ` Rich Felker [this message]
2017-01-03 21:16   ` Justin Cormack
2017-01-03 21:35     ` Rich Felker
2017-01-03 22:52       ` Justin Cormack
2017-01-03 23:17         ` Rich Felker
2017-01-03 23:33           ` Rich Felker
2017-01-03 23:53             ` Rich Felker
2017-01-04 14:33               ` Justin Cormack
2017-01-04 23:05                 ` Rich Felker

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=20170103182908.GH1555@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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 NNTP newsgroup(s).