Rubygems 0.9.5 not finding SSL package

Ruby
1

I am trying to install rails on xubuntu with the line
sudo gem install rails --include-dependencies

It terminates with this error:
ERROR: While executing gem … (Gem::Exception)
SSL is not installed on this system

I have these packages installed
libssl0.9.8
libssl-dev
openssl 0.9.8e-5ubuntu3.1
libopenssl-ruby
libopenssl-ruby1.8

I built ruby 1.8.6 from source here (as per advice elsewhere).
$ ruby -v
ruby 1.8.6 (2007-03-13 patchlevel 0) [i686-linux]
$ gem -v
0.9.5
$ uname -a
Linux xubuntu 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686
GNU/Linux

Any ideas?

Thanks,
– Mike B.

2

Has anyone completed a fresh install of ruby/rubygems/rails on ubuntu
using the the new 0.9.5 rubygems ?

– Mike B.

3

On 11/27/07, Eric H. [email protected] wrote:

At that point, RubyGems is doing the equivalent of:

ruby -e “require ‘openssl’”

I’m researching why RubyGems now seems to require OpenSSL, but haven’t
discovered the cause yet.

Signed gems are done with SSL.

-austin

4

On Nov 24, 2007, at 13:27 PM, Mike B. wrote:

openssl 0.9.8e-5ubuntu3.1
i686
GNU/Linux

Any ideas?

At that point, RubyGems is doing the equivalent of:

ruby -e “require ‘openssl’”

I’m researching why RubyGems now seems to require OpenSSL, but haven’t
discovered the cause yet.

5

On Nov 28, 2007, at 04:53 AM, Austin Z. wrote:

On 11/27/07, Eric H. [email protected] wrote:

At that point, RubyGems is doing the equivalent of:

ruby -e “require ‘openssl’”

I’m researching why RubyGems now seems to require OpenSSL, but
haven’t
discovered the cause yet.

Signed gems are done with SSL.

This appears to be happening regardless of signing of gems.

6

On Nov 29, 2007, at 15:25 PM, Eric Smith wrote:

Signed gems are done with SSL.

This appears to be happening regardless of signing of gems.

The problem is that the default installation of ruby 1.8.6 from source
isn’t picking up the OpenSSL libraries, etc… during make or make
install.

No.

RubyGems should work with or without OpenSSL. If RubyGems is not
working when you don’t have OpenSSL, it’s a RubyGems bug.

7

Eric H. wrote:

On Nov 28, 2007, at 04:53 AM, Austin Z. wrote:

On 11/27/07, Eric H. [email protected] wrote:

At that point, RubyGems is doing the equivalent of:

ruby -e “require ‘openssl’”

I’m researching why RubyGems now seems to require OpenSSL, but
haven’t
discovered the cause yet.

Signed gems are done with SSL.

This appears to be happening regardless of signing of gems.

The problem is that the default installation of ruby 1.8.6 from source
isn’t picking up the OpenSSL libraries, etc… during make or make
install.

To fix this problem, you need to do the following:

Assuming your source is at /usr/src/ruby-1.8.6

cd /usr/src/ruby-1.8.6/ext/openssl
sudo ruby extconf.rb
sudo make
sudo make install

Now you should be able to install any gem.

Eric M. Smith