From: Isaac Dunham <idunham@lavabit.com>
To: musl@lists.openwall.com
Subject: Re: guard bug for strerror_r
Date: Fri, 8 Feb 2013 10:01:25 -0800 [thread overview]
Message-ID: <20130208100125.0d6bf697.idunham@lavabit.com> (raw)
In-Reply-To: <1360344600.2983.365.camel@eris.loria.fr>
On Fri, 08 Feb 2013 18:30:00 +0100
Jens Gustedt <jens.gustedt@inria.fr> wrote:
>
> __GNU_SOURCE is defined by the gnu platform to specify the
> availability of their extensions. Unfortunately they don't have a
> finer grained tool to distinguish different types of extensions they
> provide. (BTW the same holds for gcc, that you only can tune with
> version numbers.)
>
> If I, as a user, define __GNU_SOURCE I expect to have the gnu
> extension, if I then use strerror_r I expect to have their interface,
> since this is documented like this. At least as it is now, I don't
> think I have any means to distinguish the two platforms and to know
> which version of strerror_r I would receive.
#ifdef __linux
#include <features.h> /* this is partly for this purpose */
/*including <unistd.h> would also work, and is more universal
* it's actually necessary with dietlibc, IIRC */
#if defined(__GLIBC__) && defined(__USE_GNU)
..
--
Isaac Dunham <idunham@lavabit.com>
next prev parent reply other threads:[~2013-02-08 18:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-08 16:48 Jens Gustedt
2013-02-08 16:55 ` Szabolcs Nagy
2013-02-08 17:30 ` Jens Gustedt
2013-02-08 18:01 ` Isaac Dunham [this message]
2013-02-08 18:59 ` Rich Felker
2013-02-08 19:53 ` Jens Gustedt
2013-02-08 20:01 ` Rich Felker
2013-02-08 20:31 ` Jens Gustedt
2013-02-08 20:38 ` Rich Felker
2013-02-10 23:08 ` Rob Landley
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=20130208100125.0d6bf697.idunham@lavabit.com \
--to=idunham@lavabit.com \
--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).