Yeah, I've heard other reports recently that the fastthread gem can be difficult to build on windows. For now, the simplest solution is to just find the capistrano/gateway.rb file in your capistrano installation, and remove the begin/rescue/end block at the very top (that tries to load 'fastthread'). You'll almost certainly be fine if you're using a recent patchlevel of Ruby 1.8.6.

The next Capistrano release will remove that fastthread check altogether, since it was a just crutch to work around a bug in the early 1.8.6 rubies.

- Jamis

On Apr 30, 2008, at 5:22 PM, Mark A. Richman wrote:


Hi, I am new to Capistrano. I just installed on windows via "gem
install capistrano", and when I ran the "cap" command, I got this
message:

You are running Ruby 1.8.6, which has a bug in its threading
implementation.
You are liable to encounter deadlocks running Capistrano, unless you
install
the fastthread library, which is available as a gem:
  gem install fastthread

So I ran gem install fastthread, and got this error:

Bulk updating Gem source index for: http://gems.rubyonrails.org/
Building native extensions.  This could take a while...
ERROR:  Error installing fastthread:
       ERROR: Failed to build gem native extension.

c:/ruby/bin/ruby.exe extconf.rb install fastthread
creating Makefile

nmake
'nmake' is not recognized as an internal or external command,
operable program or batch file.


Gem files will remain installed in c:/ruby/lib/ruby/gems/1.8/gems/
fastthread-1.0.1-x86-mswin32 for inspection.
Results logged to c:/ruby/lib/ruby/gems/1.8/gems/fastthread-1.0.1-x86-
mswin32/ext/fastthread/gem_make.out


Has anyone gotten capistrano and/or fastthread working on Windows? I'm
running XP SP2 with Ruby 1.8.6.

Thanks,
Mark




--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---


Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to