From: Jason West Date: 2010-09-04T00:35:10+09:00 Subject: Can't install gems (Windows) - Quick Solution I too ran into the same issue with the error message being displayed when installing gems on a new Ruby 1.9.2 (http://www.ruby-lang.org/en/downloads/) installation on the C: drive. To resolve the issue I simply right-clicked the "Start Command Prompt with Ruby" that was part of the basic install of the Ruby interpreter and selected "Run as Administrator" from the menu. Hope this helps. JLW > On Sunday, January 17, 2010 5:27 PM Sal wrote: > I am unable to install any gems now on my Windows 7 machine running > Ruby 1.9.1. Earlier today I was updating a gem and it failed. Since > then, I cannot install or update ANY gems. I tried un/reinstalling ruby > with no luck. The error is: > > ERROR: While executing gem... (Errno(EEXIST) > File exists - C: >> On Sunday, January 17, 2010 7:24 PM Luis Lavena wrote: >> Please, provide more information about your ruby installation and the >> version of RubyGems being used. >> >> ('gem env' will provide all that information) >> >> Also, provide the complete output of the gem installation command with >> debug and verbose mode turned on: >> >> gem install foobar --debug -V >> >> Paste the complete output. >> >> Help us help you. >> >> -- >> Luis Lavena >>> On Sunday, January 17, 2010 9:54 PM Alpha Blue wrote: >>> I do not think you should be using 1.9.1 on windows to begin with. I am a >>> windows system admin and it is very difficult to begin to understand how >>> to build 1.9.1 from binaries. A lot of people, especially good people >>> like Luis and Roger have gone out of their way to work on a package that >>> is built around MinGW. For windows installations we are pretty much >>> stuck with either a MinGW or cygwin. >>> >>> First, Luis is correct that you need to supply all of the information >>> for your current ruby setup. >>> >>> Personally, I would not use 1.9.1. A lot of people make the mistake in >>> wanting to use the latest and greatest and after awhile they realize the >>> difficulties with trying to find gems that are compiled not only for >>> their ruby environment but gems that include OS dependencies. With >>> 1.9.1 you need to install gems based on those dependency checks. >>> >>> So, you have a few options you should consider here. >>> >>> 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 cannot use >>> Ruby EE (enterprise edition) on a windows environment so that is 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. >>> >>> So, outlining your options here if you are bent on developing on >>> windows: >>> >>> 1.8.6 - One Click Installer (no headaches) >>> JRuby 1.4 - use Netbeans 6.8 IDE ( very few headaches) >>> >>> OR, you can do the following: >>> >>> Install VMWare or Virtualbox, create a linux distro for either CentOS >>> 5.4 OR Ubuntu 9.x, and follow numerous threads for getting your >>> development going. >>> >>> My setup is as follows: >>> >>> I develop on Windows and on Linux (CentOS and Ubuntu). On Windows I >>> have Ruby 1.8.6, Ruby 1.9.1(ming..), Jruby 1.2 and 1.4. On my vmware I >>> run two distros (centos and ubuntu) and both of those distros use Ruby >>> EE (which is very fast and stable version 1.8.7) I also use netbeans >>> 6.8 on linux and it runs fine after you set it up properly. >>> >>> I know this might be a lot of information to take in, but I can think of >>> about 5 things off the top of my head and I bet Luis can to, on what has >>> gone wrong with your environment. >>> >>> I am willing to help you out if you need it. >>> >>> -- >>> Posted via http://www.ruby-forum.com/. >>>> On Sunday, January 17, 2010 10:22 PM Sal 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 `NameError' at c:/Ruby/lib/ruby/site_ruby/1.9.1/rubygems/ >>>> command_manag >>>> er.rb:161 - uninitialized constant Gem::Commands::InstallCommand >>>> Exception `Gem::LoadError' at c:/Ruby/lib/ruby/site_ruby/1.9.1/ >>>> rubygems.rb:827 - >>>> Could not find RubyGem test-unit (>= 0) >>>> >>>> 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: >>>> c:/Ruby/lib/ruby/1.9.1/fileutils.rb:243:in `mkdir' >>>> c:/Ruby/lib/ruby/1.9.1/fileutils.rb:243:in `fu_mkdir' >>>> c:/Ruby/lib/ruby/1.9.1/fileutils.rb:217:in `block (2 levels) >>>> in mkdir_p' >>>> >>>> c:/Ruby/lib/ruby/1.9.1/fileutils.rb:215:in `reverse_each' >>>> c:/Ruby/lib/ruby/1.9.1/fileutils.rb:215:in `block in mkdir_p' >>>> c:/Ruby/lib/ruby/1.9.1/fileutils.rb:201:in `each' >>>> c:/Ruby/lib/ruby/1.9.1/fileutils.rb:201:in `mkdir_p' >>>> c:/Ruby/lib/ruby/site_ruby/1.9.1/rubygems/spec_fetcher.rb: >>>> 103:in `fetch_ >>>> spec' >>>> c:/Ruby/lib/ruby/site_ruby/1.9.1/rubygems/spec_fetcher.rb: >>>> 72:in `block i >>>> n fetch' >>>> c:/Ruby/lib/ruby/site_ruby/1.9.1/rubygems/spec_fetcher.rb: >>>> 71:in `map' >>>> c:/Ruby/lib/ruby/site_ruby/1.9.1/rubygems/spec_fetcher.rb: >>>> 71:in `fetch' >>>> c:/Ruby/lib/ruby/site_ruby/1.9.1/rubygems/ >>>> dependency_installer.rb:99:in >>>> `find_gems_with_sources' >>>> c:/Ruby/lib/ruby/site_ruby/1.9.1/rubygems/ >>>> dependency_installer.rb:192:in >>>> `find_spec_by_name_and_version' >>>> c:/Ruby/lib/ruby/site_ruby/1.9.1/rubygems/ >>>> dependency_installer.rb:213:in >>>> `install' >>>> c:/Ruby/lib/ruby/site_ruby/1.9.1/rubygems/commands/ >>>> install_command.rb:11 >>>> 8:in `block in execute' >>>> c:/Ruby/lib/ruby/site_ruby/1.9.1/rubygems/commands/ >>>> install_command.rb:11 >>>> 5:in `each' >>>> c:/Ruby/lib/ruby/site_ruby/1.9.1/rubygems/commands/ >>>> install_command.rb:11 >>>> 5:in `execute' >>>> c:/Ruby/lib/ruby/site_ruby/1.9.1/rubygems/command.rb:257:in >>>> `invoke' >>>> c:/Ruby/lib/ruby/site_ruby/1.9.1/rubygems/command_manager.rb: >>>> 132:in `pro >>>> cess_args' >>>> c:/Ruby/lib/ruby/site_ruby/1.9.1/rubygems/command_manager.rb: >>>> 102:in `run >>>>> On Sunday, January 17, 2010 10:38 PM Alpha Blue wrote: >>>>> 1. Where did you build your 1.9.1 binaries from? >>>>> >>>>> Did you use this one? >>>>> >>>>> http://github.com/oneclick/rubyinstaller >>>>> >>>>> 2. Add http://gems.github.com to your gem sources >>>>> >>>>> 3. Run gem update. >>>>> >>>>> 4. Run gem list and post your gems. >>>>> >>>>> -- >>>>> Posted via http://www.ruby-forum.com/. >>>>>> On Sunday, January 17, 2010 10:42 PM Luis Lavena wrote: >>>>>> 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 are not a >>>>>> member of Administrator group, then you are 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 >>>>>>> On Monday, January 18, 2010 2:20 AM Bill Kelly wrote: >>>>>>> Alpha Blue wrote: >>>>>>> >>>>>>> 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 are 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 have 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 is at least as well-behaved.) >>>>>>> >>>>>>> >>>>>>> Regards, >>>>>>> >>>>>>> Bill >>>>>>>> On Monday, January 18, 2010 7:09 AM Sal wrote: >>>>>>>> I am using the installer from Rubyforge. >>>>>>>> >>>>>>>> I did what you suggested but when running list I still show no gems. >>>>>>>> Weird... >>>>>>>>> On Monday, January 18, 2010 7:54 AM Sal wrote: >>>>>>>>> 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. >>>>>>>>>> On Monday, January 18, 2010 8:24 AM Alpha Blue wrote: >>>>>>>>>> Sal wrote: >>>>>>>>>> >>>>>>>>>> I will 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 will post my results. >>>>>>>>>> -- >>>>>>>>>> Posted via http://www.ruby-forum.com/. >>>>>>>>>>> On Monday, January 18, 2010 9:08 AM Alpha Blue wrote: >>>>>>>>>>> 1. Downloaded Installer from (http://rubyforge.org/frs/?group_id=167) >>>>>>>>>>> -- rubyinstaller-1.9.1-p243-rc1.exe >>>>>>>>>>> 2. Right-click (run as administrator) and execute. >>>>>>>>>>> 3. Install Directory is Ruby19 and options for add/associate are >>>>>>>>>>> checked. >>>>>>>>>>> >>>>>>>>>>> Installation finished >>>>>>>>>>> >>>>>>>>>>> C:\Users\Joel>ruby -v >>>>>>>>>>> >>>>>>>>>>> ruby 1.9.1p243 (2009-07-16 revision 24175) [i386-mingw32] >>>>>>>>>>> >>>>>>>>>>> C:\Users\Joel>path >>>>>>>>>>> >>>>>>>>>>> PATH=C:\Ruby19\bin;C:\Program Files (x86)\Common Files\Business >>>>>>>>>>> Objects\3.0\bin\ >>>>>>>>>>> NOTES\;C:\Program Files (x86)\Common Files\Business >>>>>>>>>>> Objects\3.0\bin\NOTES\DATA\; >>>>>>>>>>> C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Ruby\bin;C:\mysql;C:\ >>>>>>>>>>> wamp\bin\mysql\mysql5.1.36\bin;C:\Tcl\bin;C:\zlib;C:\Program Files >>>>>>>>>>> (x86)\Git\cmd >>>>>>>>>>> ;C:\Program Files (x86)\SWiSH >>>>>>>>>>> Studio2\burner;C:\Windows\System32\WindowsPowerShe >>>>>>>>>>> ll\v1.0\;C:\OpenSSL\;C:\OpenSSL\bin;C:\Program Files >>>>>>>>>>> (x86)\Java\jdk1.6.0_14\bin; >>>>>>>>>>> C:\Program Files (x86)\QuickTime\QTSystem\;C:\Program Files >>>>>>>>>>> (x86)\Microsoft SQL >>>>>>>>>>> Server\90\Tools\binn\;C:\Program Files (x86)\jruby-1.4.0\bin >>>>>>>>>>> >>>>>>>>>>> Note that I use many different versions of Ruby so the new installation >>>>>>>>>>> does not remove the old ruby paths still set. This could create issues >>>>>>>>>>> later on but for now I am going to leave everything the way it is. >>>>>>>>>>> >>>>>>>>>>> C:\Users\Joel>gem env >>>>>>>>>>> RubyGems Environment: >>>>>>>>>>> - RUBYGEMS VERSION: 1.3.5 >>>>>>>>>>> - RUBY VERSION: 1.9.1 (2009-07-16 patchlevel 243) [i386-mingw32] >>>>>>>>>>> - INSTALLATION DIRECTORY: C:/Ruby19/lib/ruby/gems/1.9.1 >>>>>>>>>>> - RUBY EXECUTABLE: C:/Ruby19/bin/ruby.exe >>>>>>>>>>> - EXECUTABLE DIRECTORY: C:/Ruby19/bin >>>>>>>>>>> - RUBYGEMS PLATFORMS: >>>>>>>>>>> - ruby >>>>>>>>>>> - x86-mingw32 >>>>>>>>>>> - GEM PATHS: >>>>>>>>>>> - C:/Ruby19/lib/ruby/gems/1.9.1 >>>>>>>>>>> - C:/Users/Joel/.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://gems.github.com"] >>>>>>>>>>> - REMOTE SOURCES: >>>>>>>>>>> - http://gems.rubyforge.org/ >>>>>>>>>>> - http://gems.github.com >>>>>>>>>>> >>>>>>>>>>> Note that the sources are already set correctly. If they were not set, >>>>>>>>>>> I'd have added github.com manually. >>>>>>>>>>> >>>>>>>>>>> C:\Users\Joel>gem list >>>>>>>>>>> >>>>>>>>>>> *** LOCAL GEMS *** >>>>>>>>>>> >>>>>>>>>>> No gems are listed. >>>>>>>>>>> >>>>>>>>>>> Performing "gem update --system" >>>>>>>>>>> >>>>>>>>>>> Updating RubyGems >>>>>>>>>>> Nothing to update >>>>>>>>>>> >>>>>>>>>>> Performing "gem -v" >>>>>>>>>>> 1.3.5 >>>>>>>>>>> >>>>>>>>>>> Okay, so far so good. Everything is fine so far. >>>>>>>>>>> >>>>>>>>>>> (Installation of Gems commencing) >>>>>>>>>>> >>>>>>>>>>> Installing Rails First >>>>>>>>>>> >>>>>>>>>>> C:\Users\Joel>gem install rails >>>>>>>>>>> Successfully installed rake-0.8.7 >>>>>>>>>>> Successfully installed activesupport-2.3.5 >>>>>>>>>>> Successfully installed activerecord-2.3.5 >>>>>>>>>>> Successfully installed rack-1.0.1 >>>>>>>>>>> Successfully installed actionpack-2.3.5 >>>>>>>>>>> Successfully installed actionmailer-2.3.5 >>>>>>>>>>> Successfully installed activeresource-2.3.5 >>>>>>>>>>> Successfully installed rails-2.3.5 >>>>>>>>>>> 8 gems installed >>>>>>>>>>> Installing ri documentation for rake-0.8.7... >>>>>>>>>>> Installing ri documentation for activesupport-2.3.5... >>>>>>>>>>> Installing ri documentation for activerecord-2.3.5... >>>>>>>>>>> Installing ri documentation for rack-1.0.1... >>>>>>>>>>> Installing ri documentation for actionpack-2.3.5... >>>>>>>>>>> Installing ri documentation for actionmailer-2.3.5... >>>>>>>>>>> Installing ri documentation for activeresource-2.3.5... >>>>>>>>>>> Installing ri documentation for rails-2.3.5... >>>>>>>>>>> Updating class cache with 0 classes... >>>>>>>>>>>> On Monday, January 18, 2010 9:17 AM Sal wrote: >>>>>>>>>>>> Thanks, but I 'think' I have it resolved. And....it WAS a permissions >>>>>>>>>>>> issue. I realized that a "critical" windows 7 security update was >>>>>>>>>>>> installed yesterday. Automatic updates was "magically" turned on again >>>>>>>>>>>> for some reason. >>>>>>>>>>>> >>>>>>>>>>>> After more digging, I noticed it had marked many of the directories in >>>>>>>>>>>> my /User directory as read-only. After removing the read only >>>>>>>>>>>> attribute I was able to install gems again. Gotta love Windows..... I >>>>>>>>>>>> would really like to know exactly what it did. >>>>>>>>>>>> >>>>>>>>>>>> Thanks to all for your help! >>>>>>>>>>>>> On Monday, January 18, 2010 9:19 AM Alpha Blue wrote: >>>>>>>>>>>>> I know the post above is a long one but it was necessary to showcase >>>>>>>>>>>>> some of the problems a person may encounter on windows. However, it is >>>>>>>>>>>>> all working fine with the same release that you are using. >>>>>>>>>>>>> >>>>>>>>>>>>> My suggestions is for you to uninstall the current version of ruby you >>>>>>>>>>>>> are using and check your windows paths to ensure that no traces are left >>>>>>>>>>>>> of ruby or ruby 19. >>>>>>>>>>>>> >>>>>>>>>>>>> Then download and install the latest ruby19 from the source I provided >>>>>>>>>>>>> (which is the same source you are using). Install the latest ruby19. >>>>>>>>>>>>> Download and install the latest devkit and unzip it and place it inside >>>>>>>>>>>>> C:\ruby19. >>>>>>>>>>>>> >>>>>>>>>>>>> The directory structure will be such: >>>>>>>>>>>>> >>>>>>>>>>>>> Directory of C:\Ruby19 >>>>>>>>>>>>> >>>>>>>>>>>>> 01/18/2010 09:02 AM . >>>>>>>>>>>>> 01/18/2010 09:02 AM .. >>>>>>>>>>>>> 01/18/2010 09:02 AM bin >>>>>>>>>>>>> 01/18/2010 09:02 AM devkit >>>>>>>>>>>>> 01/18/2010 08:28 AM doc >>>>>>>>>>>>> 01/18/2010 08:28 AM include >>>>>>>>>>>>> 04/11/2009 10:52 AM 304 INSTALL.txt >>>>>>>>>>>>> 01/18/2010 08:28 AM lib >>>>>>>>>>>>> 01/18/2010 08:28 AM share >>>>>>>>>>>>> 01/18/2010 08:28 AM 126,093 unins000.dat >>>>>>>>>>>>> 01/18/2010 08:26 AM 1,167,576 unins000.exe >>>>>>>>>>>>> 01/18/2010 08:28 AM 20,709 unins000.msg >>>>>>>>>>>>> 4 File(s) 1,314,682 bytes >>>>>>>>>>>>> 8 Dir(s) 291,281,985,536 bytes free >>>>>>>>>>>>> >>>>>>>>>>>>> Notice that the devkit is in the Ruby19 folder and the bin folder that >>>>>>>>>>>>> comes with the devkit is forceably copied over the Ruby19 bin which will >>>>>>>>>>>>> just add the contents into the bin directory. >>>>>>>>>>>>> >>>>>>>>>>>>> Then, once you do this you can begin installing gems. Start with the >>>>>>>>>>>>> same ones I installed for starters and use the same options. >>>>>>>>>>>>> >>>>>>>>>>>>> Always, always, always test your gems right after installation. You do >>>>>>>>>>>>> this by going to irb and then running a require "gemname" and if it is >>>>>>>>>>>>> good it will show => true. If it is bad it will show => false or give >>>>>>>>>>>>> you a lot of errors. >>>>>>>>>>>>> >>>>>>>>>>>>> If you get a lot of errors like you saw I did with mongrel above, it >>>>>>>>>>>>> just needs to be built from source. With the devkit installed, you can >>>>>>>>>>>>> do just that. >>>>>>>>>>>>> >>>>>>>>>>>>> Remember that when you need platform specific gems to declare it that >>>>>>>>>>>>> way: >>>>>>>>>>>>> >>>>>>>>>>>>> gem install "gemname" --platform x86-mingw32 >>>>>>>>>>>>> >>>>>>>>>>>>> If you need to install from a particular source, then include all of it >>>>>>>>>>>>> like I did with mongrel. >>>>>>>>>>>>> >>>>>>>>>>>>> The big question that you might ask me later on is how did I know to use >>>>>>>>>>>>> that particular gem source? Well go visit http://isitruby19.com and do >>>>>>>>>>>>> a search for the gem you want to download. People will give you the >>>>>>>>>>>>> info on what gems work and which gems do not and in this case, mongrel >>>>>>>>>>>>> had a good build listed at the following gem source I provided above. >>>>>>>>>>>>> >>>>>>>>>>>>> I hope this helps you isolate and fix your issues now. >>>>>>>>>>>>> -- >>>>>>>>>>>>> Posted via http://www.ruby-forum.com/. >>>>>>>>>>>>>> On Monday, January 18, 2010 9:30 AM Sal wrote: >>>>>>>>>>>>>> Wow, thanks! I am going to need this because I want to use Mongrel! >>>>>>>>>>>>>>> On Monday, January 18, 2010 11:23 AM Luis Lavena wrote: >>>>>>>>>>>>>>> ) >>>>>>>>>>>>>>> o: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Mongrel 1.1.5 has not been prepared for 1.9.1. Even more, the binary >>>>>>>>>>>>>>> version do not support both 1.8 and 1.9 >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> I am working on a release of 1.1.6 that support these versions. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> As for the issue related to the installation process, seems you >>>>>>>>>>>>>>> resolved the permission issue that was associated with the directory. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Next version of RubyInstaller (rc2) will not require admin privileges >>>>>>>>>>>>>>> even if you are a member of Administrator group with UAC high. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Regards, >>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>> Luis Lavena >>>>>>>>>>>>>>>> On Monday, January 18, 2010 12:20 PM Jonathan Nielsen wrote: >>>>>>>>>>>>>>>> Someone has released a patched version of mongrel 1.1.5 that will >>>>>>>>>>>>>>>> compile its extensions against 1.9.1 just fine... the link is all over >>>>>>>>>>>>>>>> the comments for mongrel on isitruby19.com, let me look real quick... >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> This one: gem install mongrel --source http://gems.rubyinstaller.org >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Works great for me (just tested it against ruby 1.9.1 on cygwin... it >>>>>>>>>>>>>>>> is a little slow as mongrel on windows tends to be for some reason, >>>>>>>>>>>>>>>> I will have to try it on my linux box later) >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> -Jonathan Nielsen >>>>>>>>>>>>>>>>> On Monday, January 18, 2010 12:52 PM Charles Oliver Nutter wrote: >>>>>>>>>>>>>>>>> We would love to know what the few headaches are for JRuby. In my >>>>>>>>>>>>>>>>> estimation, it is the easiest way by far to get Ruby running on >>>>>>>>>>>>>>>>> Windows, and we have recently spent a great deal of effort on >>>>>>>>>>>>>>>>> Windows-related issues in our bug tracker. Plus for libraries like >>>>>>>>>>>>>>>>> Mongrel or Hpricot, there is no compile phase *ever* and if you need to >>>>>>>>>>>>>>>>> write fast "native" code, there are options like java-inline. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Support for Ruby 1.9 is a work in progress, but then so is Ruby 1.9 :) >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> - Charlie >>>>>>>>>>>>>>>>>> On Monday, January 18, 2010 1:26 PM Alpha Blue wrote: >>>>>>>>>>>>>>>>>> Hi Luis, as Jonathan pointed out and I did earlier in my thread, I am >>>>>>>>>>>>>>>>>> using 1.1.6 for Mongrel from the source I outlined. It works great and >>>>>>>>>>>>>>>>>> it is fully tested for 1.9.1. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Just an fyi... >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>>> Posted via http://www.ruby-forum.com/. >>>>>>>>>>>>>>>>>>> On Monday, January 18, 2010 9:56 PM Luis Lavena wrote: >>>>>>>>>>>>>>>>>>> That 'someone' is me, so I am pretty aware of that release and its >>>>>>>>>>>>>>>>>>> limitations :-) >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> That release was done as proof of concept, but should not be used as >>>>>>>>>>>>>>>>>>> production environment since lot of tests did not complete. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> It will work, but again: I advise against it until official 1.1.6 >>>>>>>>>>>>>>>>>>> release is made. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> I am working on it but JRuby parser is still giving me some issues. >>>>>>>>>>>>>>>>>>> Once that is ironed, expect an official release with 1.9 support. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Cheers, >>>>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>>>> Luis Lavena >>>>>>>>>>>>>>>>>>>> On Monday, January 18, 2010 10:22 PM Alpha Blue wrote: >>>>>>>>>>>>>>>>>>>> Somehow, I knew that someone might have been you as soon as I posted >>>>>>>>>>>>>>>>>>>> that this morning. :) >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> You are everywhere! >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> God bless you though. You are really a god send to this community. >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Take care mate. >>>>>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>>>>> Posted via http://www.ruby-forum.com/. >>>>>>>>>>>>>>>>>>>>> On Tuesday, January 19, 2010 1:34 AM Jonathan Nielsen wrote: >>>>>>>>>>>>>>>>>>>>> OK, thanks for clarifying that 1.1.6. All I really knew about it was >>>>>>>>>>>>>>>>>>>>> it was a lot easier than patching 1.1.5 with all the RSTRING_PTRs and >>>>>>>>>>>>>>>>>>>>> whatever else like I did until I found that :) >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> -Jonathan Nielsen >>>>>>>>>>>>>>>>>>>>>> On Friday, January 29, 2010 12:53 AM senling wrote: >>>>>>>>>>>>>>>>>>>>>> Hi, >>>>>>>>>>>>>>>>>>>>>> I have installed ruby and trying to set rails environment. >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> ruby 1.8.6 (2007-09-24 patchlevel 111) [i386-mswin32] >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> RubyGems Environment: >>>>>>>>>>>>>>>>>>>>>> - VERSION: 0.9.4 (0.9.4) >>>>>>>>>>>>>>>>>>>>>> - INSTALLATION DIRECTORY: C:/Ruby/lib/ruby/gems/1.8 >>>>>>>>>>>>>>>>>>>>>> - GEM PATH: >>>>>>>>>>>>>>>>>>>>>> - C:/Ruby/lib/ruby/gems/1.8 >>>>>>>>>>>>>>>>>>>>>> - REMOTE SOURCES: >>>>>>>>>>>>>>>>>>>>>> - http://gems.rubyforge.org >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> ERROR: While executing gem ... (Gem::GemNotFoundException) >>>>>>>>>>>>>>>>>>>>>> Could not find rails (> 0) in any repository >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> I tried downloading the gem locally , still the same error >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> Updating RubyGems... >>>>>>>>>>>>>>>>>>>>>> Attempting remote update of rubygems-update >>>>>>>>>>>>>>>>>>>>>> ERROR: While executing gem ... (Gem::InstallError) >>>>>>>>>>>>>>>>>>>>>> rubygems-update requires builder >= 0 >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> I could'nt install any gems. >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> *** LOCAL GEMS *** >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> fxri (0.3.6) >>>>>>>>>>>>>>>>>>>>>> fxruby (1.6.12) >>>>>>>>>>>>>>>>>>>>>> hpricot (0.6) >>>>>>>>>>>>>>>>>>>>>> log4r (1.0.5) >>>>>>>>>>>>>>>>>>>>>> rake (0.7.3) >>>>>>>>>>>>>>>>>>>>>> sources (0.0.1) >>>>>>>>>>>>>>>>>>>>>> win32-api (1.0.4) >>>>>>>>>>>>>>>>>>>>>> win32-clipboard (0.4.3) >>>>>>>>>>>>>>>>>>>>>> win32-dir (0.3.2) >>>>>>>>>>>>>>>>>>>>>> win32-eventlog (0.4.6) >>>>>>>>>>>>>>>>>>>>>> win32-file (0.5.4) >>>>>>>>>>>>>>>>>>>>>> win32-file-stat (1.2.7) >>>>>>>>>>>>>>>>>>>>>> win32-process (0.5.3) >>>>>>>>>>>>>>>>>>>>>> win32-sapi (0.1.4) >>>>>>>>>>>>>>>>>>>>>> win32-sound (0.4.1) >>>>>>>>>>>>>>>>>>>>>> windows-api (0.2.0) >>>>>>>>>>>>>>>>>>>>>> windows-pr (0.7.2) >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> I would like to know the procedure for setting up the rails >>>>>>>>>>>>>>>>>>>>>> environment. >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> Thanks in advance >>>>>>>>>>>>>>>>>>>>>> Senling >>>>>>>>>>>>>>>>>>>>>>> On Friday, January 29, 2010 2:22 AM Gordon Thiesfeld wrote: >>>>>>>>>>>>>>>>>>>>>>> [Note: parts of this message were removed to make it a legal post.] >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> I would recommend you use the newer rubyinstaller package. >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> http://rubyinstaller.org/download.html >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> http://blog.mmediasys.com/2009/07/06/getting-started-with-rails-and-sqlite3/ >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> or: >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> http://blog.mmediasys.com/2009/07/06/getting-started-with-rails-and-mysql/ >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> Gordon >>>>>>>>>>>>>>>>>>>>>>> Submitted via EggHeadCafe - Software Developer Portal of Choice >>>>>>>>>>>>>>>>>>>>>>> AJAX Web Service Driven Customers Table With Customer Details >>>>>>>>>>>>>>>>>>>>>>> http://www.eggheadcafe.com/tutorials/aspnet/4c3d2726-d99e-4f83-9e49-0d4867b6271a/ajax-web-service-driven-customers-table-with-customer-details.aspx