[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK4o1WyWrmszFFqO1u=EWSnX-C5xgt2-ZJDhjWwr1oOTKGbpzg@mail.gmail.com>
Date: Tue, 3 Jan 2017 17:44:47 +0000
From: Justin Cormack <justin@...cialbusservice.com>
To: musl@...ts.openwall.com
Subject: libstdc++ namespace pollution
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
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)?
Justin
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
