Project

General

Profile

Actions

Bug #6325

closed

Can't install

Added by flowshine (Kurt von Laven) almost 12 years ago. Updated almost 12 years ago.

Status:
Closed
Assignee:
-
Target version:
-
ruby -v:
ruby 1.9.3p125 (2012-02-16 revision 34643) [x86_64-linux]
Backport:
[ruby-core:44464]

Description

I am trying to install RubyGems 1.8.22 and Rails 3.2.3 on Red Hat 4.4.6-3. I used RVM, and the precise sequence of commands is attached as well as my ~/.bashrc file.

Evidently my installation didn't work. Here is the output of rails --version.

/usr/lib64/ruby/site_ruby/1.8/rubygems.rb:926:in report_activate_error': Could not find RubyGem rails (>= 0) (Gem::LoadError) from /usr/lib64/ruby/site_ruby/1.8/rubygems.rb:244:in activate_dep'
from /usr/lib64/ruby/site_ruby/1.8/rubygems.rb:236:in activate' from /usr/lib64/ruby/site_ruby/1.8/rubygems.rb:1307:in gem'
from /usr/bin/rails:18


Files

Command Sequence.txt (14.7 KB) Command Sequence.txt The sequence of commands I entered and the corresponding error messages. flowshine (Kurt von Laven), 04/20/2012 04:05 AM
Bashrc.txt (391 Bytes) Bashrc.txt My ~/.bashrc file. flowshine (Kurt von Laven), 04/20/2012 04:05 AM

Updated by flowshine (Kurt von Laven) almost 12 years ago

Whoops, sorry. I meant to make the subject "Can't Install Rails."

Updated by mame (Yusuke Endoh) almost 12 years ago

  • Status changed from Open to Feedback

Hello,

ruby -v: ruby 1.9.3p125 (2012-02-16 revision 34643) [x86_64-linux]

export GEM_PATH=$GEM_HOME:/usr/lib64/ruby/gems/1.8

Are you using 1.9 interpreter with 1.8 gems?

I guess you'd better ask a question in ruby-talk.
Maybe people will tell you kindly :-)

--
Yusuke Endoh

Updated by drbrain (Eric Hodel) almost 12 years ago

"/usr/lib64/ruby/site_ruby/1.8/rubygems.rb" is not a path that RVM would create. I suspect your PATH is not configured properly. Please check which rails and ensure it matches the directory of your RVM install. You should be able to get help from ruby-talk or from the #rvm channel on chat.freenode.net.

Updated by flowshine (Kurt von Laven) almost 12 years ago

Thanks guys. It turns out the fix was to delete every Ruby-related thing I could find on my machine and then reinstall what I wanted using RVM. I posted it as a bug rather than on the help forum the way it was crashing made me suspect that there might be some deeper problem going on. Yusuke, I was indeed using the 1.9 interpreter with RubyGems 1.8.

Updated by drbrain (Eric Hodel) almost 12 years ago

  • Status changed from Feedback to Closed
Actions

Also available in: Atom PDF

Like0
Like0Like0Like0Like0Like0