From: Luis Lavena on 17 Jan 2010 22:42 On Jan 18, 12:22 am, Sal <salbass...(a)hotmail.com> wrote: > I am using the latest ruby 1.9.1 windows installer. > > gem env yields: > > RubyGems Environment: > - RUBYGEMS VERSION: 1.3.5 > - RUBY VERSION: 1.9.1 (2009-07-16 patchlevel 243) [i386-mingw32] > - INSTALLATION DIRECTORY: c:/Ruby/lib/ruby/gems/1.9.1 > - RUBY EXECUTABLE: c:/Ruby/bin/ruby.exe > - EXECUTABLE DIRECTORY: c:/Ruby/bin > - RUBYGEMS PLATFORMS: > - ruby > - x86-mingw32 > - GEM PATHS: > - c:/Ruby/lib/ruby/gems/1.9.1 > - C:/Users/Matt/.gem/ruby/1.9.1 > - GEM CONFIGURATION: > - :update_sources => true > - :verbose => true > - :benchmark => false > - :backtrace => false > - :bulk_threshold => 1000 > - :sources => ["http://gems.rubyforge.org/", "http:// > gemcutter.org"] > - REMOTE SOURCES: > -http://gems.rubyforge.org/ > -http://gemcutter.org > > Any gem install fails, but for example here is the attempt to install > rails: > > Exception `Errno::EEXIST' at c:/Ruby/lib/ruby/1.9.1/fileutils.rb:243 - > File exis > ts - C:/Users/Matt/.gem/specs/gems.rubyforge.org%80 > Exception `Errno::EEXIST' at c:/Ruby/lib/ruby/1.9.1/fileutils.rb:243 - > File exis > ts - C:/Users/Matt/.gem/specs/gemcutter.org%80 > Exception `Errno::ENOENT' at c:/Ruby/lib/ruby/1.9.1/fileutils.rb:243 - > No such f > ile or directory - C:/Users/Matt/.gem/specs/gemcutter.org%80/quick/ > Marshal.4.8 > Exception `Errno::EEXIST' at c:/Ruby/lib/ruby/1.9.1/fileutils.rb:243 - > File exis > ts - C: > Exception `Errno::EEXIST' at c:/Ruby/lib/ruby/1.9.1/fileutils.rb:219 - > File exis > ts - C: > ERROR: While executing gem ... (Errno::EEXIST) > File exists - C: > > [...] > Thank you guys so much. I appreciate nay assistance you can provide me! Please change directory into one of the gem installation directories: cd c:/Ruby/lib/ruby/gems/1.9.1 And try yo create a file there: ruby -rfileutils -e "FileUtils.touch 'foobar'" Repeat the same process with the second directory shown by gem env (C:/ Users/Matt/.gem/ruby/1.9.1) If you or Ruby cannot write to these directories, it will fail. If you installed Ruby with administrative privileges and you're not a member of Administrator group, then you're hitting a permission issue. I would recommend setting GEM_HOME and GEM_PATH environment variables to a different place (one that you have control) and try installation again. Also, please remove gemcutter from your gem sources: gem sources -r http://gemcutter.org As Gemcutter is now gems.rubyforge.org -- Luis Lavena
From: Bill Kelly on 18 Jan 2010 02:20 Alpha Blue wrote: > If you are hell bent on developing with windows, then go to the 1.8.6 > one-click installer, or move to netbeans 6.8 and jruby. You can't use > Ruby EE (enterprise edition) on a windows environment so that's not a > good option. While you could go with a 1.8.7 setup, you are probably > going to run into similar compiler issues, especially with windows 7. > And, if you are trying to use 64-bit, this is a whole other headache in > itself. Hopefully not to confuse the issue, but depending on one's requirements there are significant benefits from using 1.9.x or 1.9.2 on windows. 1.9.x provides, for the first time in FOREVER on windows ruby, a popen() that only blocks its own thread, rather than the whole process. And 1.9.2 provides Unicode path support on windows. (Last I checked, Unicode path support was only partially implemented so far in 1.9.2, but they're working on it.) Both a non-process-blocking popen() and Unicode path support are critical to my current application, so 1.9.2 is a must for me on Windows. Thankfully, so far I've found it relatively simple to build ruby from the command line using the Microsoft compiler. (Haven't tried the MinGW route, but I presume it's at least as well-behaved.) Regards, Bill
From: Sal on 18 Jan 2010 07:09 On Jan 17, 10:38 pm, Alpha Blue <jdezen...(a)gmail.com> wrote: > 1. Where did you build your 1.9.1 binaries from? I am using the installer from Rubyforge. I did what you suggested but when running list I still show no gems. Weird...
From: Sal on 18 Jan 2010 07:54 I have tried all of your suggestions and the problem persists. I was able to write in those directories (not a permissions problem), and changing the gem path/home yielded the same result. I am really baffled as this WAS working yesterday until I had issues with a gem called cucumber. Any suggestions? I am really stumped here.
From: Alpha Blue on 18 Jan 2010 08:24 Sal wrote: > On Jan 17, 10:38�pm, Alpha Blue <jdezen...(a)gmail.com> wrote: >> 1. �Where did you build your 1.9.1 binaries from? > > I am using the installer from Rubyforge. > > I did what you suggested but when running list I still show no gems. > Weird... I'll build a new package with the one from Rubyforge on Win 7 and see if I encounter any similar issues. Provide me a short list of gems you were trying to install as well. I'll post my results. -- Posted via http://www.ruby-forum.com/.
First
|
Prev
|
Next
|
Last
Pages: 1 2 3 4 5 Prev: Notifying via Terminal in Linux Next: Ruby Array to Java Script Array |