Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Build a shared openssl to link to Ruby as a stopgap to fix build issu…
…es some people are having, pending understanding why static linking isn't working.
- Loading branch information
fee1e49
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it worth pushing another tag/release just for this change or do you want to wait until we understand the problem better? Personally, I’d like to understand the root cause of the problem before we release this change.
fee1e49
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1
fee1e49
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@kevinSuttle Are you 👍 a release or waiting until we understand the problem better and fix static linking? I’d still like to try to understand why this was broken for you but not for me.
fee1e49
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@sferik Both, but mainly waiting until we understand the problem better and fix static linking. Obviously this is a bigger underlying problem.
fee1e49
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd prefer to understand the root cause, too, but static linking isn't critical either, so I think it's worth releasing as a stopgap.
fee1e49
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jeremy Okay. I won’t have time to push a release until later today or tomorrow. Feel free to do it yourself if you want it before then.
Has any of this made you reconsider your decision to remove
homebrew
openssl
support from #273? Then we could credibly go with option number 2 in #316 (delegate certificate management tocurl-ca-bundle
). It adds a bit of complexity but could prevent bigger headaches in the future, after a certificate is revoked.fee1e49
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd like homebrew integration, too, but it wasn't worth complicating our first effort.
curl-ca-bundle
doesn't install a defaultOPENSSLDIR/cert.pem
so no luck there.fee1e49
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@sferik have you tried removing homebrew OpenSSL and using the latest tagged release? It fails to compile quite consistently without this change.
fee1e49
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@wfarr Yes. I just tried that and it still works for me.
fee1e49
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay, I just tagged
v20130226
and submitted a pull requested tohomebrew
: Homebrew/legacy-homebrew#18100.