GCC 6 symbol poisoning and c++ header usage is fragile
Jonathan Wakely
jwakely.gcc@gmail.com
Thu Apr 21 11:52:00 GMT 2016
On 21 April 2016 at 12:11, Szabolcs Nagy wrote:
> the root cause is c++: c++ headers include random libc headers with
> _GNU_SOURCE ftm so all sorts of unexpected symbols are defined/declared.
Yes, I'd really like to be able to stop defining _GNU_SOURCE
unconditionally. It needs some libstdc++ and glibc changes for that to
happen, I'll be looking at it for gcc 7.
> since it's unlikely the c++ standard gets fixed (to properly specify
> the namespace rules)
Fixed how? What's wrong with the rules? (I'd like to understand what's
wrong here before I try to change anything, and I don't understand the
comment above).
More information about the Gcc
mailing list