tag:help.rubygems.org,2010-01-19:/discussions/problems/56-scriptserver-wont-run-because-of-rubygems-but-gem-commands-run-fineRubyGems.org: Discussion 2018-10-18T19:50:52Ztag:help.rubygems.org,2010-01-19:Comment/10876372010-02-23T15:19:27Z2010-02-23T15:19:27Zscript/server won't run because of RubyGems but gem commands run fine<div><p>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.</p></div>John Barnettetag:help.rubygems.org,2010-01-19:Comment/10876372010-02-23T15:29:12Z2010-02-23T15:29:35Zscript/server won't run because of RubyGems but gem commands run fine<div><p>sorry.</p>
<p>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.</p>
<p>gem version is 1.3.6, ruby is 1.8.7</p>
<p>which ruby = /opt/local/bin/ruby<br>
which gem = /usr/bin/gem<br>
which rails = /usr/bin/rails<br></p></div>scotttag:help.rubygems.org,2010-01-19:Comment/10876372010-02-23T15:38:10Z2010-02-23T15:38:10Zscript/server won't run because of RubyGems but gem commands run fine<div><p>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 <strong>system</strong>
install (upgraded to 1.3.6) of RubyGems, which is probably not a
good thing.</p>
<p>In fact, I bet if you try making sure that
<code>/usr/bin/ruby</code> is first in your path you'll find that
everything works smoothly.</p>
<p>If you're going to use Ruby from MacPorts, don't use it with the
system install of RubyGems. Follow the <a href=
"http://rubygems.org/pages/download">manual/setup.rb installation
instructions</a>, and make sure that you use
<code>/opt/local/bin/ruby</code> when you run
<code>setup.rb</code>.</p></div>John Barnettetag:help.rubygems.org,2010-01-19:Comment/10876372010-02-23T21:44:22Z2010-02-23T21:44:32Zscript/server won't run because of RubyGems but gem commands run fine<div><p>Don't know that this was the most efficient way to fix this, but
here's what I did:</p>
<p>install rubygems from macports<br>
reinstall...lots of gems (probably all of them eventually but the
ones that I needed to run this site were all I did)</p></div>Scotttag:help.rubygems.org,2010-01-19:Comment/10876372010-02-23T21:54:49Z2010-02-23T21:54:49Zscript/server won't run because of RubyGems but gem commands run fine<div><p>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.</p></div>John Barnettetag:help.rubygems.org,2010-01-19:Comment/10876372010-02-23T22:03:20Z2010-02-23T22:03:23Zscript/server won't run because of RubyGems but gem commands run fine<div><p>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.</p>
<p>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)</p></div>scott