I finally got around to taking another look at this.
The next weird thing is MacOS thinks it _is_ a .S file, even though
there's only mention of .s in the makefile.
MacOS is, of course, case-insensitive, which probably doesn't help.
On 19 August 2013 15:39, Ben Laurie b...@links.org wrote:
Thanks for this ... haven't had the chance to test it yet (travel) but will
do shortly.
On 12 August 2013 05:49, Andy Polyakov ap...@openssl.org wrote:
I'm trying to figure out why bsdmake on MacOS does this using the
standard Makefiles:
cc -c -I. -I.. -I../include -DOPENSSL_THREADS
I'm trying to figure out why bsdmake on MacOS does this using the
standard Makefiles:
cc -c -I. -I.. -I../include -DOPENSSL_THREADS -D_REENTRANT
-DDSO_DLFCN -DHAVE_DLFCN_H -Wall -pedantic -DPEDANTIC -Wno-long-long
-Wsign-compare -Wmissing-prototypes -Wshadow -Wformat -Werror
I'm trying to figure out why bsdmake on MacOS does this using the
standard Makefiles:
cc -c -I. -I.. -I../include -DOPENSSL_THREADS -D_REENTRANT
-DDSO_DLFCN -DHAVE_DLFCN_H -Wall -pedantic -DPEDANTIC -Wno-long-long
-Wsign-compare -Wmissing-prototypes -Wshadow -Wformat -Werror
-DCRYPTO_MDEBUG_ALL
