Skip to content
Discussion options

You must be logged in to vote

Hi both, thanks for reporting. Apparently this is something due to "multilib" support in OpenSSL build system. I've opened a PR to fix this: #2452

I guess that most Linux users didn't come across this because they already had OpenSSL installed on their system?

In the meantime, two different workarounds that come to my mind:

  1. Install libssl-dev via your package manager. This is much faster than having ruby-build compile its own OpenSSL, and results in all Ruby versions on this system linking to a shared, system OpenSSL version that your package manager will continue to upgrade.

  2. Run ruby-build with OPENSSL_CONFIGURE_OPTS="--libdir=lib" set. This is only a temporary workaround until ruby-…

Replies: 2 comments

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Answer selected by mislav
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
3 participants