[openssl-dev] [openssl.org #4479] OS X 10.8 (x86_64): Compile errors when using "no-asm -ansi"
noloader at gmail.com
Fri Mar 25 18:16:59 UTC 2016
> It's the fact of its being defined which indicates features - it's tested in
> the GNU headers to decide what functionality to make visible. The norm is
> just to define it, or to define it to 1; setting it to __STRICT_ANSI__ would
> be a very confusing thing to do since the whole point of defining it is to
> say that you don't want __STRICT_ANSI__.
Thanks, I parsed the comments in the header incorrectly.
> Why do you want to be able to build on an OS released in 2012 with a
> C89-only compiler? I'm probably missing something, but I'm struggling to
> understand the point of this.
I'm not sure what the reason are. But for me, as long as its a claim
or a requirement, it gets tested to ensure goals are being met.
More information about the openssl-dev