El Capitan OpenSSL
MikeMcQuaid opened this issue · 12 comments
In El Capitan OpenSSL's libraries are still provided but headers have been removed from the OS X SDKs. As a result, you should no longer encourage the use of brew link openssl --force
as clang
's default link and library paths mean that you may end up using newer Homebrew OpenSSL headers but link against the older, system version.
For a reproduction example see https://gist.github.com/tdsmith/4b502c5cc6e7d358acdf
Thanks for the heads up, @MikeMcQuaid. I will mention it in the El Cap guide which I'll write when the OS is released.
Hey @drduh , not related to this issue but how compatible is this guide with El Capitan in general? Wish I've seen this repo when I was on Yosemite :(
@mixania I've gone through this guide on El Capitan without any hitches.
any revision for el capitan is planned ?
@nickpellant thanks, nice to know
Hey @poulagah I am planning to clone this into an updated El Cap guide in the next week or so. Stay tuned!
@drduh there were some issues with the SIP on el Cap, and also unloading some services causes CPU spikes. Not sure when you plan on releasing the guide, and I didn't want to open a seperate issue, but if you would consider starting a new repo with release info that would be awesome. Great guide BTW. Cheers.
Thanks for letting me know, @SKGrimes. I will try and get a preliminary El Cap guide by the end of the week, time permitting.
Is this still accurate for Sierra?
FYI, ondoing brew install --force openssl
Homebrew outputs:
...
Generally there are no consequences of this for you. If you build your
own software and it requires this formula, you'll need to add to your
build variables:
LDFLAGS: -L/usr/local/opt/openssl/lib
CPPFLAGS: -I/usr/local/opt/openssl/include
...
So maybe that solves this issue for Sierra as well?