From: Alexander Monakov <amonakov@ispras.ru>
To: musl@lists.openwall.com
Subject: Re: the prototype decl of memcpy/memcmp/calloc/free shouldnot in sched.h
Date: Sat, 1 Nov 2014 23:49:23 +0300 (MSK) [thread overview]
Message-ID: <alpine.LNX.2.00.1411012348070.27387@monopod.intra.ispras.ru> (raw)
In-Reply-To: <20141101170236.GJ22465@brightrain.aerifal.cx>
> I think the problem may be that GCC activates _GNU_SOURCE by default
> for C++. Am I right about this?
Yes, that's true; see for example http://lwn.net/Articles/590504/ and
https://gcc.gnu.org/onlinedocs/libstdc++/faq.html#faq.predefined
Alexander
next prev parent reply other threads:[~2014-11-01 20:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-31 3:03 the prototype decl of memcpy/memcmp/calloc/free should not " 黄建忠
2014-10-31 3:24 ` Rich Felker
2014-10-31 3:42 ` the prototype decl of memcpy/memcmp/calloc/free shouldnot " 黄建忠
2014-11-01 16:22 ` Szabolcs Nagy
2014-11-01 17:02 ` Rich Felker
2014-11-01 20:49 ` Alexander Monakov [this message]
2014-11-02 4:48 ` 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=alpine.LNX.2.00.1411012348070.27387@monopod.intra.ispras.ru \
--to=amonakov@ispras.ru \
--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).