From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: musl detection by preprocessor
Date: Fri, 8 Feb 2013 18:07:41 +0100 [thread overview]
Message-ID: <20130208170741.GX6181@port70.net> (raw)
In-Reply-To: <1360342301.2983.361.camel@eris.loria.fr>
* Jens Gustedt <jens.gustedt@inria.fr> [2013-02-08 17:51:41 +0100]:
> Am Freitag, den 08.02.2013, 17:41 +0100 schrieb Szabolcs Nagy:
> > * Jens Gustedt <jens.gustedt@inria.fr> [2013-02-08 17:28:07 +0100]:
> > > In short I have some problem where they (the gnus) deviate from
> > > standard interfaces, here this was triggered by their different
> > > iterface for strerror_r. Now the musl compiler wrapper doesn't allow
> > > to distinguish a linux system with glibc or with musl (or at least I
> > > didn'find one).
> > >
> > > Inspecting the wrapper, it looks quite easy to add something like
> > >
> > > -D__MUSL__=000909UL
> > >
> >
> > can you use #ifdef __GLIBC__ ?
>
> Hm, I don't think that this comes timely enough. Where would this be
> defined, probably in some header file that I'd include, no?
>
> I'd like to distinguish the platform as early as possible, ideally
> *before* I include any files, such that I can base decisions on which
> files to include only on #defines that the pure compiler provides.
>
ok now i understand what you want
i think you should use featuretest macros
to get a subset of the interfaces
(eg specify -D_BSD_SOURCE for all bsd things
or -D_POSIX_C_SOURCE=200809L for posix etc)
you can check the default setting in
include/features.h
strerror_r may be bad to provide under _GNU_SOURCE
but by that logic we should not provide ptrintf
under _GNU_SOURCE either as the gnu printf is
non-conformant but musl's printf is
next prev parent reply other threads:[~2013-02-08 17:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-08 16:28 Jens Gustedt
2013-02-08 16:41 ` Szabolcs Nagy
2013-02-08 16:51 ` Jens Gustedt
2013-02-08 17:07 ` Szabolcs Nagy [this message]
2013-02-08 18:55 ` Rich Felker
2013-02-08 20:12 ` Jens Gustedt
2013-02-08 20:19 ` 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=20130208170741.GX6181@port70.net \
--to=nsz@port70.net \
--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).