On Fri, Mar 25, 2016 at 12:49 PM, Richard Levitte via RT <r...@openssl.org>
wrote:
> Vid Fre, 25 Mar 2016 kl. 16.31.14, skrev noloa...@gmail.com:
>> To configure:
>>
>> ./config shared no-asm -ansi -D_DEFAULT_SOURCE=__STRICT_ANSI__
>>
>> I'm not sure if Configure should set _DEFAULT_SOURCE=__STRICT_ANSI__
>> automatically.
>
> Why do you give it the value __STRICT_ANSI__? All documentation I find
> suggests
> it's enough to simply define it. See man page feature_test_macros(7) on Linux
> (at least)
>
> The alternative is, of course, to define _DEFAULT_SOURCE in the files where
> -ansi becomes a problem.
That was based on examining /usr/include/features.h and the comment
for _DEFAULT_SOURCE:
_DEFAULT_SOURCE The default set of features (taking precedence
over __STRICT_ANSI__).
How do you convey features by just defining it? It seems like it needs
an argument, like _DEFAULT_SOURCE=__STRICT_ANSI__ or
_DEFAULT_SOURCE=_POSIX_SOURCE.
But its definitely not my area of expertise. I've never had to define to before.
Jeff
--
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
