It seems the most recent change to ruby-build 20191002 homebrew formula to require openssl@1.1 breaks the install of Ruby versions that are < 2.4 (those require openssl 1.0.2q)
So, for macOS users who install ruby-build via homebrew, they will get openssl@1.1 installed as well.
If they then try to run rbenv install 2.1.10 for instance, it will fail with:
Last 10 log lines:
The Ruby openssl extension was not compiled.
ERROR: Ruby install aborted due to missing extensions
Configure options used:
--prefix=/Users/username/.rbenv/versions/2.1.10
--with-openssl-dir=/usr/local/opt/openssl@1.1
--with-readline-dir=/usr/local/opt/readline
CC=clang
CFLAGS= -O3 -Wno-error=shorten-64-to-32
LDFLAGS=-L/Users/username/.rbenv/versions/2.1.10/lib
CPPFLAGS=-I/Users/username/.rbenv/versions/2.1.10/include
Yeah, I know older versions are EOL but they still get used in some environments.
Seems like changing https://github.com/rbenv/ruby-build/blob/master/bin/ruby-build#L1023 to only check for openssl and not `openssl@1.1 could potentially fix this?
It seems the most recent change to ruby-build 20191002 homebrew formula to require openssl@1.1 breaks the install of Ruby versions that are < 2.4 (those require openssl 1.0.2q)
So, for macOS users who install ruby-build via homebrew, they will get openssl@1.1 installed as well.
If they then try to run
rbenv install 2.1.10for instance, it will fail with:Yeah, I know older versions are EOL but they still get used in some environments.
Seems like changing https://github.com/rbenv/ruby-build/blob/master/bin/ruby-build#L1023 to only check for
openssland not `openssl@1.1 could potentially fix this?