rbenv / ruby-build Public
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build Ruby 2.3 fails due to an openssl error #1321
Comments
Ruby 2.3 didn't support OpenSSL 1.1.x. and it's already EOL status.
I'm not sure what means this. The definition of ruby-build for Ruby 2.3 uses openssl-1.0.x: https://github.com/rbenv/ruby-build/blob/master/share/ruby-build/2.3.8#L1 |
The ruby-build openSUSE package requires I have removed this requirement in the openSUSE ruby-build package and installed I am not sure if there is a nice way to fix this problem apart of what I did (which is not really nice and uses a modified package). I know Ruby 2.3 is already in EOL status, but it is still used in many places, such as programming challenges like Google Code Jam and Hacker Earth (for those kind of things I find ruby-build + rbenv really useful). |
Presently, it only uses local openssl-1.0 on OS X, because the check |
I'm sorry you had trouble. Building older versions of Ruby is often hard. We do not publish linux packages for ruby-build, so we can't control what people list as dependencies in those packags. If a package declares To ensure that the proper openssl version gets used when building any version of Ruby on linux:
Unfortunately, we are choosing to not automatically handle any of this in ruby-build because building openssl on linux is complex and best left to the user. |
Thanks for following up. Unlike the original bug, I am not using a packaged version of ruby-build, and am on Debian rather than Suse. This issue shows up on Google, so I felt some commentary would be useful to anyone else finding it as I did. It is not possible for a package to pull in both OpenSSL 1.1 and 1.0 headers as, unlike the library files, these share a path. As numerous libraries now depend on 1.1, swapping which header package is installed (as I have done in the past) is rather unpleasant, and (ab)using the existing installation script as described is relatively simpler than figuring out my own steps for building a copy of 1.0 someplace and linking it. I figured I'd document this possibility for myself/anyone else who comes across this issue. |
I've been trying this method and can't get it to work, I've got my 1.0.2u version in But the build process seems to insist on using the version in
Any help or pointers would be appreciated :) |
Resolved, simplest method was to install RVM (https://rvm.io/) and run |
@mt-ftooth Unless you had But I'm glad you found a workaround! |
This solved it for me on Ubuntu 20.04 |
seems very strange. |
I get an openssl error when trying to install Ruby 2.3.X. I have successfully installed 2.4.1, 2.5.5 and 2.6.2. It seems openssl 1.1 doesn't support Ruby < 2.3 but openssl 1.1 is required by ruby-build.
operative system: openSUSE Leap 15.1
openssl version: OpenSSL 1.1.0i-fips 14 Aug 2018
ruby-build version: 20190401
rbenv version: 1.1.1
It may be related to #850
Log rbenv install 2.3.3
The text was updated successfully, but these errors were encountered: