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 08:02
Justin Collins wrote:
> 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

very useful, thanks!

--
Wybo

From: Brian Candler on 3 Dec 2009 08:53
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/.

From: Ryan Davis on 3 Dec 2009 14:21

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

that's old rdoc. not sure how/why you're hitting that. But `sudo gem install rdoc` and try rio again.


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