On Jul 25, 6:33 pm, toddv <[EMAIL PROTECTED]> wrote:
> SuSE Enterprise Linux 10 SP1 Solution
>
> I downloaded and built openssl-0.9.8e.tar.gz, because SuSE Enterprise
> Linux 10 doesn't necessarily name the OpenSSL libraries the names that
> might be expected by the Open Source community (e.g. Ruby).  ( I had
> started trying to make symbolic links but quickly abandoned that
> idea.)
>
> Then I rebuilt ruby-1.8.6.tar.gz and all was well.
>
> appserver:~/setup_dir/ruby-1.8.6 # irb
> irb(main):001:0> require 'openssl'
> => true
> irb(main):002:0>
>
> Thanks!
> --toddv
>
> On Jul 25, 3:13 pm, Eno <[EMAIL PROTECTED]> wrote:
>
> > On Jul 25, 6:03 pm, "Alexey Verkhovsky" <[EMAIL PROTECTED]>
> > wrote:
>
> > > Those bindings come with Ruby, not as a separate package.
> > > You get this error in two cases:
>
> > > 1. You build your own Ruby, and openssl-devel package is not installed
> > > at build time. Fix: install openssl-devel and rebuild.
>
> > > 2. You are using a precompiled Ruby, but openssl package is not
> > > installed on the server. Fix: install openssl.
>
> > In my case, I had built ruby from source initially and it did not have
> > openssl support.
>
> > Then I installed openssl from source.
>
> > Then I re-configured and rebuilt ruby from source (yes, I ran "make
> > clean") before the build.
>
> > The result is:
>
> > $ irb
> > irb(main):001:0> require 'openssl'
> > LoadError: no such file to load -- openssl
> >         from (irb):1:in `require'
> >         from (irb):1
> > irb(main):002:0>

I too had this openssl problem.  I solved it by installing ruby using
YaST instead of manually.  Also, YaST  and rubygem-sqlite solved a
problem I had compiling the db bindings.  Note: I had to add an online
source to yast from http://en.opensuse.org/Mirrors_Released_Version#USA.
--Matt Scilipoti


--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---

Reply via email to