Sasa Ebach wrote:
>> I'm sorry, I meant to say that you can run `gem` instead of `gem.bat` to 
>> get this information.  I think it is `ruby c:\ruby\bin\gem env`.
> 
> Of course, I should have thought of that.
> 
> Here we go:
> 
> C:\Documents and Settings\Sasa>ruby e:\Develop\ruby\bin\gem env
> RubyGems Environment:
>    - RUBYGEMS VERSION: 0.9.4.5 (0.9.4.5)
>    - RUBY VERSION: 1.8.6 (2007-09-24 patchlevel 111) [i386-mswin32]
>    - INSTALLATION DIRECTORY: E:/Develop/ruby/lib/ruby/gems/1.8
>    - RUBY EXECUTABLE: E:/Develop/ruby/bin/ruby.exe
>    - RUBYGEMS PLATFORMS:
>      - ruby
>      - x86-mswin32-60
>    - GEM PATHS:
>       - E:/Develop/ruby/lib/ruby/gems/1.8
>    - GEM CONFIGURATION:
>       - :update_sources => true
>       - :verbose => true
>       - :benchmark => false
>       - :backtrace => false
>       - :bulk_threshold => 1000
>    - REMOTE SOURCES:
>       - http://gems.rubyforge.org
> 
> Does this help?
> 
> ruby e:\Develop\ruby\bin\gem install rails --no-rdoc --no-ri (this 
> worked)
> 
> -se


That mean you solve the gem error you was having :-)

Please, do the same steps to update rubygems:

ruby e:\Develop\ruby\bin\gem update --system --source 
http://segment7.net

In that way you will grab the new version that features the corrected 
.bat files :-)

If you find that some gems don't work, try reinstalling them (gem 
install <gemname>).

With latest release some of the issue with the stub scripts for Windows 
got fixed.

Regards,

Luis
-- 
Posted via http://www.ruby-forum.com/.