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
Some gems are not ready for ruby1.9. Have you checked that?
···
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]
$
--
Iñaki Baz Castillo <ibc@aliax.net>
that's old rdoc. not sure how/why you're hitting that. But `sudo gem install rdoc` and try rio again.
···
On Dec 3, 2009, at 03:55 , Wybo Dekker wrote:
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
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
John W Higgins wrote:
You can use my fork at GitHub - wishdev/rio: A facade for most of the standard ruby classes that deal with I/O; Rio also provides an application level interface which allows many common I/O idioms to be expressed succinctly to get a 1.9 compliant
version (well at least it works for me) - it's not a gem at the moment but
"ruby setup.rb" from the directory should get it working for you.
Thanks John - but I've decided to go back to ruby-1.8 and wait for a more mature version.
···
--
Wybo
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.
···
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)
--
Iñaki Baz Castillo <ibc@aliax.net>
Wybo Dekker wrote:
(I assumed that, where 1.9.1 currently is the recommended ruby version,
It's not recommended by everybody 
···
--
Posted via http://www.ruby-forum.com/\.