Nice find, we should give it a try as a workaround until the openssl license issue improves (hopefully sooner than later)
On Thursday, November 26, 2015 at 11:44:20 AM UTC+1, Christian Nassau wrote: > > On 26.11.2015 10:31, Volker Braun wrote: > > Yes, thats because Apple decided (in their infinite wisdom) to not > > include openssl headers in El Capitan, so we can't link against OSX's > > openssl library even though it is present on the system. > > It seems Xcode comes equipped with its own version of the headers: > /Applications/Xcode.app/Contents//Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift-migrator/sdk/MacOSX.sdk/usr/include/openssl > > > > Would it make sense to try building against those, as a fallback solution? > > > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
