Spencer Roach wrote:
···
On 8/20/10 12:00 AM, "Caio Chassot" <dev@caiochassot.com> wrote:
what was wrong. I guess you don't even need to `make install` again,
just nuke the unwanted gem installation in site_ruby.Again, the paths:
* /usr/local/lib/ruby/1.9.1/rubygems # <== good
* /usr/local/lib/ruby/site_ruby/1.9.1/rubygems # <== badFair warning: This may only apply to my system. Think twice before you
go `rm -rf`-happy on yours.Thanks for this! That was the solution I needed...works like a charm
now!
Worked great for me too -- thx.
--
Posted via http://www.ruby-forum.com/\.