script/server won't run because of RubyGems but gem commands run fine
Scott C Reynolds
Mac OSX Leopard
script/server yields the following:
Rails requires RubyGems >= . Please install RubyGems and try again: http://rubygems.rubyforge.org
(no version number is included in the message, which seems odd). gem commands seem to be working fine.
Comments are currently closed for this discussion. You can start a new one.
Support Staff 2 Posted by John Barnette on 23 Feb, 2010 03:19 PM
Any concrete information? What version of Ruby are you running? Of RubyGems? Of Rails? I'm running Rails 2.3.5 on Ruby 1.8.7 with RubyGems 1.3.6 without a problem.
3 Posted by scott on 23 Feb, 2010 03:29 PM
sorry.
rails 2.2.2 for this particular site. rails'd up a new site to test on rails 2.3.5 and got the same error, this time with a gem version number (1.3.2) in the message.
gem version is 1.3.6, ruby is 1.8.7
which ruby = /opt/local/bin/ruby
which gem = /usr/bin/gem
which rails = /usr/bin/rails
Support Staff 4 Posted by John Barnette on 23 Feb, 2010 03:38 PM
Okay, thanks for the extra info. Based on playing One Of These Things Is Not Like The Other with your paths, I'd say that you're using a MacPorts install of Ruby with the system install (upgraded to 1.3.6) of RubyGems, which is probably not a good thing.
In fact, I bet if you try making sure that
/usr/bin/rubyis first in your path you'll find that everything works smoothly.If you're going to use Ruby from MacPorts, don't use it with the system install of RubyGems. Follow the manual/setup.rb installation instructions, and make sure that you use
/opt/local/bin/rubywhen you runsetup.rb.5 Posted by Scott on 23 Feb, 2010 09:44 PM
Don't know that this was the most efficient way to fix this, but here's what I did:
install rubygems from macports
reinstall...lots of gems (probably all of them eventually but the ones that I needed to run this site were all I did)
Support Staff 6 Posted by John Barnette on 23 Feb, 2010 09:54 PM
Glad it's working for you. The general rule of thumb here is to never install your primary Ruby from source on Mac OS X without immediately using that ruby to install a corresponding instance of RubyGems.
John Barnette closed this discussion on 23 Feb, 2010 09:54 PM.
scott re-opened this discussion on 23 Feb, 2010 10:03 PM
7 Posted by scott on 23 Feb, 2010 10:03 PM
my concern, in case anyone has additional insight, is that I had a perfectly functional rails/ruby environment until today. I haven't done any rails dev in a few weeks, and in that time I haven't added/subtracted anything from the environment, so unless a os x update broke it...I'm not sure what happened.
good info though for when I set up new (which I will do soon I think, because I feel like this was less than optimal a solution)
Nick Quaranto closed this discussion on 13 Mar, 2010 06:40 PM.