Prev: How to use tls1 but not sslv2/3 in https?
Next: ruby-1.9.1: require 'rio' fails
From: Wybo Dekker on 3 Dec 2009 06:55
Since moving to ruby-1.9.1-p243, when I try to install the rio gem, I get:

$ sudo gem install -r rio
Successfully installed rio-0.4.2
1 gem installed
Installing ri documentation for rio-0.4.2...
Updating class cache with 2676 classes...
Installing RDoc documentation for rio-0.4.2...
ERROR: While executing gem ... (NameError)
uninitialized constant Generators::SM
$ ruby -v
ruby 1.9.1p243 (2009-07-16 revision 24175) [i686-linux]
$

It's not only a documentation problem: when I run this:

#!/usr/bin/env ruby
require 'rubygems'
require 'rio'
puts 'done'

I get (from the require 'rio', fatally):

/usr/local/lib/ruby/gems/1.9.1/gems/rio-0.4.2/lib/rio/base.rb:54: warning:
undefining `object_id' may cause serious problem
/usr/local/lib/ruby/gems/1.9.1/gems/rio-0.4.2/lib/rio/base.rb:54: warning:
undefining `__send__' may cause serious problem
/usr/local/lib/ruby/gems/1.9.1/gems/rio-0.4.2/lib/rio/uri/file.rb:93:in
`<module:PATTERN>': uninitialized constant URI::REGEXP::PATTERN::PARAM (NameError)
from /usr/local/lib/ruby/gems/1.9.1/gems/rio-0.4.2/lib/rio/uri/file.rb:88:in
`<module:REGEXP>'
from /usr/local/lib/ruby/gems/1.9.1/gems/rio-0.4.2/lib/rio/uri/file.rb:87:in
`<module:URI>'
from /usr/local/lib/ruby/gems/1.9.1/gems/rio-0.4.2/lib/rio/uri/file.rb:46:in
`<top (required)>'
from /usr/local/lib/ruby/gems/1.9.1/gems/rio-0.4.2/lib/rio/rl/base.rb:39:in
`require'
from /usr/local/lib/ruby/gems/1.9.1/gems/rio-0.4.2/lib/rio/rl/base.rb:39:in
`<top (required)>'
from /usr/local/lib/ruby/gems/1.9.1/gems/rio-0.4.2/lib/rio/rl/builder.rb:39:in
`require'
from /usr/local/lib/ruby/gems/1.9.1/gems/rio-0.4.2/lib/rio/rl/builder.rb:39:in
`<top (required)>'
from /usr/local/lib/ruby/gems/1.9.1/gems/rio-0.4.2/lib/rio/factory.rb:45:in
`require'
from /usr/local/lib/ruby/gems/1.9.1/gems/rio-0.4.2/lib/rio/factory.rb:45:in
`<top (required)>'
from /usr/local/lib/ruby/gems/1.9.1/gems/rio-0.4.2/lib/rio.rb:56:in `require'
from /usr/local/lib/ruby/gems/1.9.1/gems/rio-0.4.2/lib/rio.rb:56:in `<class:Rio>'
from /usr/local/lib/ruby/gems/1.9.1/gems/rio-0.4.2/lib/rio.rb:53:in `<module:RIO>'
from /usr/local/lib/ruby/gems/1.9.1/gems/rio-0.4.2/lib/rio.rb:52:in `<top
(required)>'
from t:3:in `require'
from t:3:in `<main>'



--
Wybo

From: Iñaki Baz Castillo on 3 Dec 2009 07:03
El Jueves, 3 de Diciembre de 2009, Wybo Dekker escribió:
> Since moving to ruby-1.9.1-p243, when I try to install the rio gem, I get:
>
> $ sudo gem install -r rio
> Successfully installed rio-0.4.2
> 1 gem installed
> Installing ri documentation for rio-0.4.2...
> Updating class cache with 2676 classes...
> Installing RDoc documentation for rio-0.4.2...
> ERROR: While executing gem ... (NameError)
> uninitialized constant Generators::SM
> $ ruby -v
> ruby 1.9.1p243 (2009-07-16 revision 24175) [i686-linux]
> $

Some gems are not ready for ruby1.9. Have you checked that?

--
Iñaki Baz Castillo <ibc(a)aliax.net>

From: Wybo Dekker on 3 Dec 2009 07:39
I�aki Baz Castillo wrote:

> Some gems are not ready for ruby1.9. Have you checked that?

ah - no! Where do find that?

(I assumed that, where 1.9.1 currently is the recommended ruby version, it would
be safe to use that - no warnings seen)
--
Wybo

From: Justin Collins on 3 Dec 2009 07:56
Wybo Dekker wrote:
> I�aki Baz Castillo wrote:
>
>> Some gems are not ready for ruby1.9. Have you checked that?
>
> ah - no! Where do find that?
>
> (I assumed that, where 1.9.1 currently is the recommended ruby
> version, it would be safe to use that - no warnings seen)

Here: http://isitruby19.com/rio

-Justin

From: Iñaki Baz Castillo on 3 Dec 2009 08:02
El Jueves, 3 de Diciembre de 2009, Wybo Dekker escribió:
> Iñaki Baz Castillo wrote:
> > Some gems are not ready for ruby1.9. Have you checked that?
>
> ah - no! Where do find that?
>
> (I assumed that, where 1.9.1 currently is the recommended ruby version, it
> would be safe to use that - no warnings seen)

There are lots of gems (or ruby libraries) not ready for Ruby 1.9. some of
them don't compile as they include C extensions not adapted for Ruby1.9. Some
others don't work as Ruby1.9 is not full backwards compatible with Ruby1.8.

You should check it in the project page.


--
Iñaki Baz Castillo <ibc(a)aliax.net>

 |  Next  |  Last
Pages: 1 2
Prev: How to use tls1 but not sslv2/3 in https?
Next: ruby-1.9.1: require 'rio' fails