Arnt Gulbrandsen <[email protected]> a écrit, le 2014-03-18 à k h 03 : > And then there's openssl, for which Apple is basically > saying "do not use". I found http://stackoverflow.com/questions/7406946 > and I suppose that absent patches, I'll just disable that warning, too. > Because I'm definitely not going to spend time on Apple Common Crypto.
I wonder if the compromise would be to provide a way to compile with a
different OpenSSL install? I know that all usually happens (and that’s
the limit of what I know about build systems) through autoconf for stuff
like Apache ("--with-ssl=/usr/local/somepath"). Would jam be able to do
something like that with minimal effort?
Paul
P.-S. In case it might be useful, I’ve attached the output from jam
since that’s actually the main build system you use.
jam.out
Description: Binary data
