Date: Tue, 3 Jan 2017 16:35:52 -0500 From: Rich Felker <dalias@...c.org> To: musl@...ts.openwall.com Subject: Re: libstdc++ namespace pollution On Tue, Jan 03, 2017 at 09:16:29PM +0000, Justin Cormack wrote: > On 3 January 2017 at 18:29, Rich Felker <dalias@...c.org> wrote: > > 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. :) > > This particular issue only happens with Musl, it includes more... That might be a bug/unwanted behavior on musl's side then. Could you help me check? I'd be happy to remove namespace-polluting cruft that's not actually needed to meet what applications can reasonably expect from _GNU_SOURCE. Rich
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.