Re: musl detection by preprocessor

[Jens Gustedt <jens.gustedt@inria.fr>]

[-- Attachment #1: Type: text/plain, Size: 1275 bytes --]

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.

Jens

-- 
:: INRIA Nancy Grand Est :: http://www.loria.fr/~gustedt/   ::
:: AlGorille ::::::::::::::: office Nancy : +33 383593090   ::
:: ICube :::::::::::::: office Strasbourg : +33 368854536   ::
:: ::::::::::::::::::::::::::: gsm France : +33 651400183   ::
:: :::::::::::::::::::: gsm international : +49 15737185122 ::



[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]