On Thu, May 12, 2011 at 12:59 PM, Martin H. [email protected] wrote:
Apparently, there is something wrong my Ruby compilation.
I have compiled Ruby 1.9.1 and 1.9.2 on Mac, Ubuntu, and Redhat. Same
result. I suspect a missing dependency that don’t raise the alarm.
Do you have OpenSSL devel packages installed? Are they found by
./configure?
–
Phillip G.
Though the folk I have met,
(Ah, how soon!) they forget
When I’ve moved on to some other place,
There may be one or two,
When I’ve played and passed through,
Who’ll remember my song or my face.
maasha@maxwell:~/Install/src/ruby-1.9.2-p180$ dpkg -l | grep -i ssl
ii libcurl4-openssl-dev 7.18.2-8lenny4
Development files and documentation for libc
ii libssl-dev 0.9.8g-15+lenny11
SSL development libraries, header files and
ii libssl0.9.8 0.9.8g-15+lenny11
SSL shared libraries
ii openssl 0.9.8g-15+lenny11
Secure Socket Layer (SSL) binary and related
ii openssl-blacklist 0.4.2
list of blacklisted OpenSSL RSA keys
ii ssl-cert 1.0.23
simple debconf wrapper for OpenSSL
should do the trick, though, since you seem to have everything in
order, otherwise.
–
Phillip G.
Though the folk I have met,
(Ah, how soon!) they forget
When I’ve moved on to some other place,
There may be one or two,
When I’ve played and passed through,
Who’ll remember my song or my face.
That’s highly specific to your environment, but a “find libssl0.9.8”
should help.
Third: I tried to manually compile ext/openssl and recompile ext/digest,
but still no Digest::Base.
Yeah, those are stubs (i.e. they don’t do anything). There once were
export restrictions in the US on almost all cryptography (technically,
crypto is a weapon as far as US export law is concerned).
–
Phillip G.
Though the folk I have met,
(Ah, how soon!) they forget
When I’ve moved on to some other place,
There may be one or two,
When I’ve played and passed through,
Who’ll remember my song or my face.
Yeah, those are stubs (i.e. they don’t do anything). There once were
export restrictions in the US on almost all cryptography (technically,
crypto is a weapon as far as US export law is concerned).
maasha@maxwell:~/Install/src/ruby-1.9.2-p180$ dpkg -l | grep libssl
ii libssl-dev 0.9.8g-15+lenny11
SSL development libraries, header files and
ii libssl0.9.8 0.9.8g-15+lenny11
SSL shared libraries
Mac: are you using a “ports” system?
Yes, openssl @1.0.0d (devel, security) is installed
I am beginning to suspect that ssl is not the problem. openssl and
libssl and libssl-dev is installed on all systems. There is no options
to select alternative paths to libssl in Ruby’s configure script.
Digest::Base does not work with neither my compilations of ruby1.9.1 and
ruby1.9.2 OR with the precompiled Ruby1.9 Debian and Ubuntu packages.
–with-PACKAGE is the correct one, where “PACKAGE” should be replaced
with “openssl” (so, adding the path was incorrect information on my
part).
But /usr/lib is included per default, right?
It should, yes.
Yeah, those are stubs (i.e. they don’t do anything). There once were
export restrictions in the US on almost all cryptography (technically,
crypto is a weapon as far as US export law is concerned).
Crazy!
Kinda. In the Bad Old Days nobody wanted to hand strong cryptography
to the Soviets. The easiest way was classifying crypto as weapons,
instead of creating a new category (since weapons could be traded with
NATO partners, obviously).
–
Phillip G.
Though the folk I have met,
(Ah, how soon!) they forget
When I’ve moved on to some other place,
There may be one or two,
When I’ve played and passed through,
Who’ll remember my song or my face.
Though the folk I have met,
(Ah, how soon!) they forget
When I’ve moved on to some other place,
There may be one or two,
When I’ve played and passed through,
Who’ll remember my song or my face.
Can we somehow test if Ruby has SSL support - without using digest -
which appears to be broken?
Sure. Try to access a website that uses HTTPS, like so:
irb(main):001:0> require ‘httpclient’
ArgumentError: undefined class/module Digest::Base
from internal:lib/rubygems/custom_require:29:in require' from <internal:lib/rubygems/custom_require>:29:inrequire’
from
/home/maasha/Install/src/Martin/lib/ruby/gems/1.9.1/gems/httpclient-2.2.0.2/lib/httpclient.rb:11:in <top (required)>' from <internal:lib/rubygems/custom_require>:33:inrequire’
from internal:lib/rubygems/custom_require:33:in rescue in require' from <internal:lib/rubygems/custom_require>:29:inrequire’
from (irb):1
from ./irb:12:in `’
OK, so something ssl is probably fubar. It is strange that it appears to
be a problem with both the precompiled debian packages and my ruby
do-it-yourself compile.
Grrr. I need some systematic approach to track down this issue.
It grabs source code for Ruby implementations, and compiles it.
–
Phillip G.
Though the folk I have met,
(Ah, how soon!) they forget
When I’ve moved on to some other place,
There may be one or two,
When I’ve played and passed through,
Who’ll remember my song or my face.
It grabs source code for Ruby implementations, and compiles it.
–
Phillip G.
Though the folk I have met,
(Ah, how soon!) they forget
When I’ve moved on to some other place,
There may be one or two,
When I’ve played and passed through,
Who’ll remember my song or my face.
I’ve used this link for installing RVM on Ubuntu, it’s very well-written
and easy to follow.