From: matt@... (matt neuburg) Date: 2009-02-26T00:54:23+09:00 Subject: Re: error trying to install ruby gems 1.3.1 7stud -- wrote: > matt neuburg wrote: > > 7stud -- wrote: > > > >> uninitialized constant Gem::Etc > > > > Google sez: > > > > > 26&atid=575> > > > > But what I don't get is: I've got gem 1.3.1 and I never had this problem > > (same system as you). Perhaps this is a difference between installing > > from source and installing from gem. > > > > m. > > Hi, > > Thanks for the response. My gem questions usually go unanswered. In my > short experience with the gem system, it is a ponderously slow(bulk > updating) broken piece of junk. The gem website here: > > http://www.rubygems.org/read/chapter/3#page14 > > says: > > ------- > If your RubyGems version is 0.8.5 or later, you can upgrade to the > latest version with: > > gem update --system > ------ > > I have ruby-gems 0.9.4 installed, and a couple of weeks ago I tried to > update ruby-gems using that command, and I posted here that I got this > error: > > > $ sudo gem update --system > Password: > Updating RubyGems... > Attempting remote update of rubygems-update > Successfully installed rubygems-update-1.0.0 > Updating version of RubyGems to 1.3.1 > ERROR: While executing gem ... (Errno::ENOENT) > No such file or directory - > /usr/lib/ruby/gems/1.8/gems/rubygems-update-1.3.1 > > What version of ruby do you have installed? > > $ ruby -v > ruby 1.8.2 (2004-12-25) [universal-darwin8.0] I'm no big expert, but at least we have similar systems so a comparison might be useful in tracking this stuff down. I am using, ruby 1.8.6 (2008-03-03 patchlevel 114) [powerpc-darwin8.9.0] My working ruby is in /usr/local. I've left the built-in ruby in place, so I also have /usr/bin/ruby: ruby 1.8.2 (2004-12-25) [powerpc-darwin8.0] But I don't use it. But I don't think that's the issue. When you get an error message warning that there is no directory rubygems-update-1.3.1, I tend to think that this is because you are supposed to have such a directory. Your quoted material says "Successfully installed rubygems-update-1.0.0"; but the current version is 1.3.1. So that must be what rubygems is looking for. I *do* have such a directory: /usr/local/lib/ruby/gems/1.8/gems/rubygems-update-1.3.1 I think you need that before you can proceed. Of course mine is in a different place because my ruby is in a different place. So you could probably get things working by following this procedure (but use sudo): $ gem install rubygems-update $ update_rubygems However, you don't really need to do that, because, as the Google-found ruby-forge page I cited says, there was a bug, it has been fixed, and you can check out working code from the trunk. So your setup.rb approach should also now work. m. -- matt neuburg, phd = matt@tidbits.com, http://www.tidbits.com/matt/ Leopard - http://www.takecontrolbooks.com/leopard-customizing.html AppleScript - http://www.amazon.com/gp/product/0596102119 Read TidBITS! It's free and smart. http://www.tidbits.com