So, I downloaded the latest.zip file, extracted it, opened a command prompt in the directory and ran rake. Several minutes later, the compile/install of ruby failed. I think it has something to do with my RUBYOPT (which is now set to -rubygems) environment variable. Here''s the relevant output: make[1]: Leaving directory `/c/Share/installer3/sandbox/ruby_build'' "C:/Share/installer3/sandbox/msys/bin/bash.exe" --login -i -c "make install" ./miniruby.exe ../ruby_1_8/instruby.rb --dest-dir="" --extout=".ext" --make="make" --mflags="- --un ix" --make-flags=" --unix" --installed-list .installed.list --mantype="man" installing binary commands installing command scripts installing library scripts installing headers installing manpages installing extension objects installing extension scripts ruby setup.rb install --no-ri --no-rdoc ruby: no such file to load -- ubygems (LoadError) rake aborted! Command failed with status (1): [ruby setup.rb install --no-ri --no-rdoc...] (See full trace by running task with --trace) =Will Green
On Sat, Mar 29, 2008 at 7:45 PM, Will Green <will at hotgazpacho.org> wrote:> So, I downloaded the latest.zip file, extracted it, opened a command > prompt in the directory and ran rake. > > Several minutes later, the compile/install of ruby failed. I think it > has something to do with my RUBYOPT (which is now set to -rubygems) > environment variable. Here''s the relevant output: > > make[1]: Leaving directory `/c/Share/installer3/sandbox/ruby_build'' > "C:/Share/installer3/sandbox/msys/bin/bash.exe" --login -i -c "make install" > ./miniruby.exe ../ruby_1_8/instruby.rb --dest-dir="" --extout=".ext" > --make="make" --mflags="- --un > ix" --make-flags=" --unix" --installed-list .installed.list --mantype="man" > installing binary commands > installing command scripts > installing library scripts > installing headers > installing manpages > installing extension objects > installing extension scripts > ruby setup.rb install --no-ri --no-rdoc > ruby: no such file to load -- ubygems (LoadError) > rake aborted! > Command failed with status (1): [ruby setup.rb install --no-ri --no-rdoc...] > > (See full trace by running task with --trace) > >Thank you Will. We need to blame RubyGems for this. I''m checking it right now, but that change will not be available until next official release :-( Regards, -- Luis Lavena Multimedia systems - Human beings, who are almost unique in having the ability to learn from the experience of others, are also remarkable for their apparent disinclination to do so. Douglas Adams
On Sun, Mar 30, 2008 at 7:27 AM, Luis Lavena <luislavena at gmail.com> wrote:> > Thank you Will. > > We need to blame RubyGems for this. >Ok, I just fixed this in Installer3 codebase. RubyGems installation now includes empty RUBYOPT to avoid loading of existing rubygems and thus, halting the install procedure.> I''m checking it right now, but that change will not be available until > next official release :-(I can''t replicate the direct behavior since we are "shelling" two levels deep, so normal installation of RubyGems via command line do not raises this :-( Anyway, just solved it ;-) Regards, -- Luis Lavena Multimedia systems - Human beings, who are almost unique in having the ability to learn from the experience of others, are also remarkable for their apparent disinclination to do so. Douglas Adams