From: Lei Zhang <zhanglei.april@gmail.com>
To: Luca Barbato <lu_zero@gentoo.org>
Cc: gentoo-musl@lists.gentoo.org
Subject: Re: [gentoo-musl] [GSoC] _GNU_SOURCE in C++
Date: Tue, 14 Jun 2016 17:17:52 +0800 [thread overview]
Message-ID: <CAOYuCc2b2v2wBLGjBzkGRNdKe1gV8uSqnCLFxnxyodZuQ9Ym5g@mail.gmail.com> (raw)
In-Reply-To: <4228046b-02f1-1b65-f56d-6e79347e4390@gentoo.org>
2016-06-14 17:12 GMT+08:00 Luca Barbato <lu_zero@gentoo.org>:
> On 14/06/16 10:28, Lei Zhang wrote:
>> 2016-06-14 16:10 GMT+08:00 Felix Janda <felix.janda@posteo.de>:
>>> Take a look at the discussion at
>>>
>>> http://www.openwall.com/lists/musl/2014/04/15/3
>>
>> And some view from the LLVM side:
>>
>> http://article.gmane.org/gmane.comp.compilers.clang.devel/46390
>>
>> IMHO, the real problem is the abuse of _GNU_SOURCE by C++ compiler.
>> The decisions made by LLVM and musl both look reasonable to me.
>>
>
> -U_GNU_SOURCE would make you get through the problem for the time being?
>
> Given you aren't using libstdc++ in that case, assuming libcxx does not
> have the need probably might be the easiest workaround.
Unfortunately libc++ depends on this macro as well:
http://lists.llvm.org/pipermail/cfe-dev/2016-June/049447.html
I'm imagining some ugly hacks on LLVM now...
Lei
next prev parent reply other threads:[~2016-06-14 9:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-14 7:44 [gentoo-musl] [GSoC] _GNU_SOURCE in C++ Lei Zhang
2016-06-14 8:10 ` Felix Janda
2016-06-14 8:28 ` Lei Zhang
[not found] ` <4228046b-02f1-1b65-f56d-6e79347e4390@gentoo.org>
2016-06-14 9:17 ` Lei Zhang [this message]
[not found] ` <20302d1d-92ff-1c4b-8939-08894c3589ca@gentoo.org>
2016-06-14 9:35 ` Lei Zhang
[not found] ` <8e7cafd9-97c7-6ca1-ad3f-95bdb0060ce0@gentoo.org>
2016-06-14 11:48 ` Lei Zhang
[not found] ` <e1f362ee-7755-9a54-78e3-19e0733ebd3b@gentoo.org>
2016-06-15 1:45 ` Lei Zhang
[not found] ` <19f9f66f-5dd4-786a-3b29-0a57c407548e@gentoo.org>
2016-06-16 3:36 ` Lei Zhang
[not found] ` <1c93fa87-e2c3-2737-1222-ae93003e21ad@gentoo.org>
2016-06-16 12:47 ` Lei Zhang
[not found] ` <7d6fa9d6-1134-1d2a-1d06-33029b82429d@gentoo.org>
2016-06-16 13:42 ` Lei Zhang
2016-06-17 11:12 ` Lei Zhang
2016-06-17 11:13 ` Lei Zhang
[not found] ` <37117cc0-2af1-306d-6ec5-d8d37d8c588c@gentoo.org>
2016-06-17 12:44 ` Lei Zhang
2016-06-21 4:54 ` Lei Zhang
2016-06-22 13:21 ` Lei Zhang
2016-06-22 13:54 ` Lei Zhang
2016-06-22 14:02 ` Lei Zhang
2016-06-14 9:55 ` Felix Janda
[not found] ` <20160615033804.GA2473@gmail.com>
2016-06-15 3:55 ` Lei Zhang
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=CAOYuCc2b2v2wBLGjBzkGRNdKe1gV8uSqnCLFxnxyodZuQ9Ym5g@mail.gmail.com \
--to=zhanglei.april@gmail.com \
--cc=gentoo-musl@lists.gentoo.org \
--cc=lu_zero@gentoo.org \
/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