[openssl-dev] [openssl.org #4479] OS X 10.8 (x86_64): Compile errors when using "no-asm -ansi"

2016-06-08 Thread Matt Caswell via RT
Status as per ticket 4480. Closing this ticket. Matt -- Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4479 Please log in as guest with password guest if prompted -- openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev

[openssl-dev] [openssl.org #4479] OS X 10.8 (x86_64): Compile errors when using "no-asm -ansi"

2016-05-31 Thread Rich Salz via RT
So what is left to do here, or should this ticket be closed? -- Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4479 Please log in as guest with password guest if prompted -- openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev

Re: [openssl-dev] [openssl.org #4479] OS X 10.8 (x86_64): Compile errors when using "no-asm -ansi"

2016-03-25 Thread Jeffrey Walton
On Fri, Mar 25, 2016 at 2:28 PM, Richard Levitte wrote: > In message > on Fri, > 25 Mar 2016 14:16:59 -0400, Jeffrey Walton said: > > noloader> > Why do you want to be able to build on

Re: [openssl-dev] [openssl.org #4479] OS X 10.8 (x86_64): Compile errors when using "no-asm -ansi"

2016-03-25 Thread Richard Levitte
In message on Fri, 25 Mar 2016 14:16:59 -0400, Jeffrey Walton said: noloader> > Why do you want to be able to build on an OS released in 2012 with a noloader> > C89-only compiler? I'm probably missing

Re: [openssl-dev] [openssl.org #4479] OS X 10.8 (x86_64): Compile errors when using "no-asm -ansi"

2016-03-25 Thread Jeffrey Walton
> 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

Re: [openssl-dev] [openssl.org #4479] OS X 10.8 (x86_64): Compile errors when using "no-asm -ansi"

2016-03-25 Thread Jeremy Farrell
On 25/03/2016 17:01, Jeffrey Walton wrote: On Fri, Mar 25, 2016 at 12:49 PM, Richard Levitte via RT 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

Re: [openssl-dev] [openssl.org #4479] OS X 10.8 (x86_64): Compile errors when using "no-asm -ansi"

2016-03-25 Thread Jeffrey Walton
On Fri, Mar 25, 2016 at 12:49 PM, Richard Levitte via RT 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

Re: [openssl-dev] [openssl.org #4479] OS X 10.8 (x86_64): Compile errors when using "no-asm -ansi"

2016-03-25 Thread noloa...@gmail.com via RT
On Fri, Mar 25, 2016 at 12:49 PM, Richard Levitte via RT 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

[openssl-dev] [openssl.org #4479] OS X 10.8 (x86_64): Compile errors when using "no-asm -ansi"

2016-03-25 Thread Richard Levitte via RT
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

[openssl-dev] [openssl.org #4479] OS X 10.8 (x86_64): Compile errors when using "no-asm -ansi"

2016-03-25 Thread noloa...@gmail.com via RT
Working from Master at 7793e17440539b71 on OS X 10.8. Also see http://stackoverflow.com/questions/13870489/is-inline-asm-part-of-the-ansi-c-standard. $ KERNEL_BITS=64 ./config shared no-asm -ansi ... $ make -k ... cc -DDSO_DLFCN -DHAVE_DLFCN_H -DOPENSSL_THREADS -DOPENSSL_NO_STATIC_ENGINE