From: "Jörg Krause" <jkrause@posteo.de>
To: musl@lists.openwall.com
Subject: Re: why is there no __MUSL__ macro?
Date: Thu, 11 Sep 2014 15:33:16 +0200 [thread overview]
Message-ID: <5411A49C.20808@posteo.de> (raw)
In-Reply-To: <20140911123800.GI21835@port70.net>
On 09/11/2014 02:38 PM, Szabolcs Nagy wrote:
> * J?rg Krause <jkrause@posteo.de> [2014-09-11 14:02:59 +0200]:
>> On 09/11/2014 01:17 PM, Szabolcs Nagy wrote:
>>> then _testing_ for conformance issues is the second try
>>> if the default fails
>> What do you mean with testing for concormance?
> eg glibc scanf uses "%a" for its own extension by default
> and c99 behaviour is only provided with appropriate cflags
>
> if your project depends on %a scanf then you may need to
> test for this conformance issue (instead of ifdef __GLIBC__
> because they may change the behaviour later or the cflag
> might not work on an older version etc)
I see. But I can avoid the GNU specific bevahiour by undefining
_GNU_SOURCE if I want POSIX-conformance. In this case I do not need to
test, but can rely on the libc of being conformal. Do I have this right?
eg, in FFmpeg/libavutils uses strerror_r which is implemented as a
XSI-compliant and a GNU-specific version. If I want to be sure to get
the XSI-compliant version, I unset _GNU_SOURCE and set
_XOPEN_SOURCE=600. So I do not need any further testing here, right?
next prev parent reply other threads:[~2014-09-11 13:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-11 11:00 Jörg Krause
2014-09-11 11:09 ` Laurent Bercot
2014-09-11 11:17 ` Szabolcs Nagy
2014-09-11 12:02 ` Jörg Krause
2014-09-11 12:38 ` Szabolcs Nagy
2014-09-11 13:33 ` Jörg Krause [this message]
2014-09-11 14:48 ` Szabolcs Nagy
2014-09-11 14:30 ` Christian Neukirchen
2014-09-11 11:17 ` Jens
2014-09-11 12:24 ` Jörg Krause
2014-09-11 14:53 ` Isaac Dunham
2014-09-12 7:39 ` Jörg Krause
2014-09-11 14:47 ` Natanael Copa
2014-09-12 7:35 ` Jörg Krause
2014-09-12 15:37 ` 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=5411A49C.20808@posteo.de \
--to=jkrause@posteo.de \
--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).