2.3.1 build fails on Ubuntu 18.04 with libssl-dev installed #1964

huwd · 2018-06-23T14:06:39Z

huwd
Jun 23, 2018

Hey folks,
I'm getting a The Ruby openssl extension was not compiled. Error when trying to build Ruby 2.3.1.
The warning and docs have been helpful but unfortunately i'm still being prompted to install libssl-dev even thought it exists on my machine.

Anything I can do to help debug this further or perhaps force it to check a path with a flag?

System

rbenv version: rbenv 1.1.1-37-g1c772d5
ruby-build version: RUBY_BUILD_VERSION="20180618"
OS:

$ lsb_release -a 
Distributor ID:	Ubuntu
Description:	Ubuntu 18.04 LTS
Release:	18.04
Codename:	bionic

libssl-dev version

$ apt-cache policy libssl-dev
libssl-dev:
  Installed: 1.1.0g-2ubuntu4
  Candidate: 1.1.0g-2ubuntu4
  Version table:
 *** 1.1.0g-2ubuntu4 500
        500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
        100 /var/lib/dpkg/status

Steps to reproduce

rbenv install 2.3.1.

Output

Downloading ruby-2.3.1.tar.bz2...
-> https://cache.ruby-lang.org/pub/ruby/2.3/ruby-2.3.1.tar.bz2
Installing ruby-2.3.1...

BUILD FAILED (Ubuntu 18.04 using ruby-build 20180618)

Inspect or clean up the working tree at /tmp/ruby-build.20180623143746.4802
Results logged to /tmp/ruby-build.20180623143746.4802.log

Last 10 log lines:
installing rdoc:              /home/user/.rbenv/versions/2.3.1/share/ri/2.3.0/system
installing capi-docs:         /home/user/.rbenv/versions/2.3.1/share/doc/ruby
The Ruby openssl extension was not compiled.
ERROR: Ruby install aborted due to missing extensions
Try running `apt-get install -y libssl-dev` to fetch missing dependencies.

Configure options used:
  --prefix=/home/user/.rbenv/versions/2.3.1
  LDFLAGS=-L/home/user/.rbenv/versions/2.3.1/lib 
  CPPFLAGS=-I/home/user/.rbenv/versions/2.3.1/include

Answered by aesyondu

Jan 7, 2020

sudo apt install libssl1.0-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package libssl1.0-dev is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'libssl1.0-dev' has no installation candidate

@aristotelesbr2014 Could you try this #1199 (comment)

I used this specifically:

On Ubuntu 19 (or any version I guess), lets install old openssl 1.0 on custom folder and then use argument options when installing ruby.

$ cd ~/src
$ wget https://www.openssl.org/source/openssl-1.0.2s.tar.gz
$ tar xvzf openssl-1.0.2s.tar.gz
$ cd openssl-…

View full answer

huwd · 2018-06-23T15:45:41Z

huwd
Jun 23, 2018
Author

Following on from a diffferent error message on #1207
I can confirm installing libssl1.0-dev sorts the problem
sudo apt install libssl1.0-dev

Does the suggestion need to be improved, or is this some ubuntu wierdness?

0 replies

IRobL · 2018-06-24T01:01:44Z

IRobL
Jun 24, 2018

Interesting, great fix @huwd! I was facing this issue as well, and I believe this thread in rbenv faced the same issue about a month ago: rbenv/rbenv#1081

0 replies

huwd · 2018-06-25T08:25:45Z

huwd
Jun 25, 2018
Author

I'm a little unclear on how SSL dependencies work across Linux, but if someone more experienced either with Rbenv or SSL dependencies doesn't mind having a quick chat I'm happy to put in a PR that either changes the warning message to sudo apt install libssl1.0-dev or see if I can add a conditional check to render the correct message for 18.04.

@IRobL can I confirm that you're also running 18.04?

0 replies

IRobL · 2018-06-25T12:53:19Z

IRobL
Jun 25, 2018

I made this observation while operating on a fresh install of Debian 9.

On Debian, It seems as though installing libssl1.0-dev bumps away libssl-dev and then installing libssl-dev bumps away libssl1.0-dev.

I haven't even glanced at the rbenv codebase, but this behavior of the packages makes me suspect that ruby-build's dependency check is explicitly looking for proof of libssl1.0-dev and isn't actually acknowledging when a (likely) compatible library is installed and ready for use?

0 replies

CoryWritesCode · 2018-06-28T20:28:48Z

CoryWritesCode
Jun 28, 2018

Is there a workaround for mac users. I think apt is mainly a linux command.

0 replies

CoryWritesCode · 2018-06-29T12:26:51Z

CoryWritesCode
Jun 29, 2018

Found a fix for Mac High Sierra by brew uninstall --force <dependencies> (like openssl, ruby-build, and even readline, and postgres@) and then reinstalling them.

0 replies

huwd · 2018-07-13T09:20:15Z

huwd
Jul 13, 2018
Author

@CoryWritesCode sorry only just saw that, glad you found a solution.
Sounds like unless they can improve the error messages we've all got a way out here - should I close this thread?

0 replies

CoryWritesCode · 2018-07-13T11:22:05Z

CoryWritesCode
Jul 13, 2018

I think so @huwd!

0 replies

murilolopes · 2018-07-24T14:29:49Z

murilolopes
Jul 24, 2018

Thank so much @huwd

0 replies

cybergizer · 2018-07-25T18:36:09Z

cybergizer
Jul 25, 2018

Thank you @huwd it worked!

0 replies

VAggrippino · 2018-12-02T21:51:01Z

VAggrippino
Dec 2, 2018

Why is this closed?

The workaround by @huwd is great, but most people aren't going to know that and not everyone will find their way here by goog like I did.

I understand that @CoryWritesCode found a Mac solution, but this issue references installation on Ubuntu. I thought a PR to change the error message seemed like a reasonable solution.

0 replies

vishgoel007 · 2019-02-10T10:57:44Z

vishgoel007
Feb 10, 2019

This worked for me sudo apt-get install -y libreadline-dev .

0 replies

aristotelesbr · 2019-09-30T16:58:46Z

aristotelesbr
Sep 30, 2019

sudo apt install libssl1.0-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package libssl1.0-dev is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'libssl1.0-dev' has no installation candidate

0 replies

aesyondu · 2020-01-07T06:16:21Z

aesyondu
Jan 7, 2020

sudo apt install libssl1.0-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package libssl1.0-dev is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'libssl1.0-dev' has no installation candidate

@aristotelesbr2014 Could you try this #1199 (comment)

I used this specifically:

On Ubuntu 19 (or any version I guess), lets install old openssl 1.0 on custom folder and then use argument options when installing ruby.

$ cd ~/src
$ wget https://www.openssl.org/source/openssl-1.0.2s.tar.gz
$ tar xvzf openssl-1.0.2s.tar.gz
$ cd openssl-1.0.2s
$ mkdir ~/.rubies/openssl-1.0.2s
$ ./config --prefix=$HOME/.rubies/openssl-1.0.2s --shared
$ make
$ make install
$ RUBY_CONFIGURE_OPTS=--with-openssl-dir=$HOME/.rubies/openssl-1.0.2s rbenv install 2.3.1

However I'm running on another issue when I run bundle install:

$ gem install bundler
ERROR:  Could not find a valid gem 'bundler' (>= 0), here is why:
          Unable to download data from https://rubygems.org/ - SSL_connect returned=1 errno=0 state=error: certificate verify failed (https://api.rubygems.org/specs.4.8.gz)

EDIT: Found this as well

rubygems/rubygems#2415 (comment)

export SSL_CERT_DIR=/etc/ssl/certs
export SSL_CERT_FILE=/etc/ssl/certs/ca-certificates.crt
gem install bundler

and I was able to gem install bundler

0 replies

josvazg · 2020-08-12T17:51:55Z

josvazg
Aug 12, 2020

@aesyondu fix worked for me on Ubuntu 20.04. In my cases gem install bundler worked right after without further fixes.

Thanks!

0 replies

nolanlawson · 2022-04-30T20:22:22Z

nolanlawson
Apr 30, 2022

@aesyondu I've scoured the internet, and your technique is the only one I've found for successfully installing older versions of Ruby like 3.0.3 or 2.7.2 on Ubuntu 22.04. Thank you!

One small fix: it should be mkdir -p ~/.rubies/openssl-1.0.2s (with the -p) since ~/.rubies may not exist.

1 reply

pnomolos May 17, 2022

If you're installing reasonably recent versions of Ruby such as 3 or even 2.7 then you're going to want to use the latest version of OpenSSL 1.1 rather than OpenSSL 1.0. The latest one in the 1.1 series from https://www.openssl.org/source/ should be fine, and you'll have to adjust paths as necessary.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

2.3.1 build fails on Ubuntu 18.04 with libssl-dev installed #1964

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 16 comments 1 reply

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

Select a reply

2.3.1 build fails on Ubuntu 18.04 with libssl-dev installed #1964

System

Steps to reproduce

Output

Replies: 16 comments · 1 reply

huwd Jun 23, 2018 Author

huwd Jun 25, 2018 Author

huwd Jul 13, 2018 Author

Replies: 16 comments 1 reply

huwd
Jun 23, 2018
Author

huwd
Jun 25, 2018
Author

huwd
Jul 13, 2018
Author