/usr/bin/gem:3:in `require': no such file to load

ruby-talk
1

Ok, I removed Ruby 1.8-2 and installed Ruby 1.8-3 from source (./configure, make, make install). Everything seemed to be fine until I tried to start gem that I previously installed. Now gem tells me:

/usr/bin/gem:3:in `require': no such file to load

If I try to run Rails, I get the same error.

What am I missing here??? If I install standardly from source, shouldn't I get all the lib required?

Please advice on this, I am kind of stuck. O_o

2

I would do a reinstall of gems if I was you.

do a #ruby setup.rb or ruby install.rb, in rubygems directory.

then do gem update & hope for the best.

3

Tony wrote:

Ok, I removed Ruby 1.8-2 and installed Ruby 1.8-3 from source (./configure, make, make install). Everything seemed to be fine until I tried to start gem that I previously installed. Now gem tells me:

/usr/bin/gem:3:in `require': no such file to load

If I try to run Rails, I get the same error.

What am I missing here??? If I install standardly from source, shouldn't I get all the lib required?

Please advice on this, I am kind of stuck. O_o

I have a problem that may be related to yours. I do not know which version of rubygems you use, but in my case, the combination of ruby 1.8.3 and rubygems 0.8.11 does not work, ie gives the error message that you got. My solution/work-around was downgrading rubygems to 0.8.10. Everything just started to work again after that. You might want to give it a try.

4

Guys, I had the same error message when I updated to Ruby 1.8.3.
Reinstalling gem has resolved the issue.

HTH
Antonio

ยทยทยท

On 11/23/05, Lars Broecker <Lars.Broecker@imk.fraunhofer.de> wrote:

Tony wrote:
> Ok, I removed Ruby 1.8-2 and installed Ruby 1.8-3 from source
> (./configure, make, make install). Everything seemed to be fine until I
> tried to start gem that I previously installed. Now gem tells me:
>
> /usr/bin/gem:3:in `require': no such file to load
I have a problem that may be related to yours. I do not know which
version of rubygems you use, but in my case, the combination of ruby
1.8.3 and rubygems 0.8.11 does not work, ie gives the error message that
you got. My solution/work-around was downgrading rubygems to 0.8.10.
Everything just started to work again after that. You might want to give
it a try.