Rails version error - related to PATH?

Hi all

I followed these instructions

some a few weeks ago to get Rails up and running on my Mac. No problems.

Then I had some wierd issues to my PATH being forgotten about a week
ago, which I managed to resolve (don’t remember the exact steps).
Yesterday my Mac crashed :frowning: and it seemed to lose some path info. One of
the results (I’m assuming) is that an app that used to run just fine,
now gives this error when I start Mongrel:

Exiting
/usr/local/lib/ruby/site_ruby/1.8/rubygems.rb:246:in `activate’: can’t
activate rails (= 1.2.6), already activated rails-1.2.3]
(Gem::Exception)

This has coincided with my path issue, so I’m associating the two
events. My path is currently set to:

/usr/local/bin:/usr/local/sbin:/usr/local/mysql/bin:/usr/bin:/usr/sbin:/bin:/sbin

Any suggestions? Is this a path issue?

Thx
Nick

Sounds like what I went through about a year or two ago. I had
installed Ruby with ports or something, then, later when a new
release was announced, I installed that by building from source.

Sorry, don’t remember which one I did first, but I remember seeing
strange PATH issues every time I rebooted. I had to hunt down and
kill all the old executables (ruby, rake, gem, etc) that were being
added to my path and that seemed to clear it up.

Hope that helps.


James M.

Talk about cryptic errors. The problem was a missing gem.

Arfon S. wrote:

Nick C. wrote:

Talk about cryptic errors. The problem was a missing gem.

Which gem?!!

I managed to fix it by installing the rconv gem.

Hope this helps.

Nick C. wrote:

Talk about cryptic errors. The problem was a missing gem.

Which gem?!!

Which gem?!!

rflickr was missing for me.