similar to: ERROR: Error installing mongrel:

Hi, I can''t install Mongrel on Ruby 1.8.6 (patchlevel 279), using Windows XP. My environment: C:\ruby18>gem environment RubyGems Environment: - RUBYGEMS VERSION: 1.2.0 - RUBY VERSION: 1.8.6 (2008-07-17 patchlevel 279) [i386-mingw32] - INSTALLATION DIRECTORY: c:/ruby18/lib/ruby/gems/1.8 - RUBY EXECUTABLE: c:/ruby18/bin/ruby.exe - EXECUTABLE DIRECTORY: c:/ruby18/bin -

Something suddenly went wrong in my ruby install. When installing Mongrel on my Windows XP laptop, it incorrectly tries to build it as a native extension. I don''t even get the selection where I can choose to install a compiled version. I would appreciate any help/links or similar, as I frankly don''t understand what''s going on and why I dont get the usual selection box.

Hi all, I''d really appreciate some help with this... As you see below, I tried to install mongrel after updating my gems, but I get the error shown: sudo gem install mongrel Select which gem to install for your platform (i486-linux) 1. mongrel 1.0.1 (ruby) 2. mongrel 1.0.1 (mswin32) 3. mongrel 1.0 (mswin32) 4. mongrel 1.0 (ruby) 5. Skip this gem 6. Cancel installation > 1

When I run rake test:units I get this error: 292 tests, 350 assertions, 2 failures, 13 errors rake aborted! Command failed with status (1): [/usr/local/bin/ruby -I"lib:test" "/ usr/loc...] This error just showed up yesterday --- I have no idea how I caused it. Here is my gem list in case that helps: actionmailer (2.3.2, 2.2.2) actionpack (2.3.2, 2.2.2) activerecord (2.3.2, 2.2.2)

I try to install passenger on win XP sp3 I have installed - ruby 1.8.6 (2008-08-11 patchlevel 287) [i386-mswin32] - gem version 1.3.1 without problems. I don''t have a web server installed yet, and no database. I don''t have any microsoft compiler on my machine, and it looks as though passenger requires it (?) What am I doing wrong? Thanks, Amir -------------- This is what I

Is anybody testing mongrel on ruby 1.9. I just tried installing mongrel on trunk 1.9 and trunk rubygems and got this error compiling fastthread: /Users/stephen/dev/ruby/1.9_trunk/bin/ruby extconf.rb install mongrel --no-rdoc creating Makefile make gcc -I. -I/Users/stephen/dev/ruby/1.9_trunk/include/ruby-1.9/i686-darwin8.10.1 -I/Users/stephen/dev/ruby/1.9_trunk/include/ruby-1.9 -I.

Heya Folks- This is mainly for Zed and Mentalguy. I have been playing with the new release of rubygems 0.9.0.8 and I have a major problem with the requirement that fastthread needs to be required before thread. Just requiring rubygems and then requiring fastthread right after that will throw the error: ez _blog $ ruby require ''rubygems'' require

It looks like I got too creative in 0.6.1 and consequently ran afoul of a bug in the Ruby interpreter. 0.6.2 works around the bug and should be entirely stable at this point. Thanks to Young Hyun for his help in coming up with test cases. == what? fastthread is a Ruby library which provides a faster (and non-memory-leaking) C implementation of the concurrency primitives from stdlib''s

== NOW A new version of fastthread, the library providing better implementations of the classes in thread.rb, has been released. Please note that fastthread is only for Ruby 1.8, not JRuby or any other Ruby implementation (most of them don''t need it anyway!). == WHY The existing implementation of Mutex, Queue, etc. in thread.rb is slow. fastthread''s is faster (and bypasses

I''m running jruby trunk which has integrated rubygems 1.0.0 and when I try and install mongrel with gem it blows up when the fastthread dependency tries to do a native compilation. I couldn''t find a copy of the gemspec in the svn checkout but looking at the one installed when gem installing mongrel didn''t show any platform differentiation. There is platform

I''ve just committed fastthread 0.5.3, which finally gives us a working SizedQueue (which hadn''t really ever worked in previous versions). Mostly it was just a matter of refactoring Queue and SizedQueue into a single class behind the scenes, so I could move the signalling of the SizedQueue-specific condition variable inside the queue''s critical section. Failing to do so

Well, just when I thought I was out of the fastthread business... Okay, in brief: fastthread is a Ruby extension which re-implements the primitives in Ruby''s thread.rb in C. It was merged into 1.8.6, replacing the old thread.rb implementation, but the version that was merged had a couple serious bugs. So -- now I release fastthread 1.0, which is basically the Ruby 1.8.6 version with

Hi All, I have an app making extensive use of Mutex and was concerned about the memory leak I have read about. I saw some sample code to reproduce the problem here: http://pastie.caboo.se/10194 So I thought I would run it myself to see the problem. I do not see a memory leak when using the sample code, but if I require "fastthread" before "thread" using fastthread (0.6.4.1)

I just realized -- if fastthread can be included while Mutex-using code is already running, then the definition and replacement of the classes needs to happen atomically. Otherwise, it creates a race condition where a thread can e.g. end up seeing an incompletely defined Mutex class or none at all. fastthread 0.6.1 addresses this by defining the classes and then atomically swapping the constant

Hi, A quick search didn''t explain what fastthread is, and how it relates to mongrel. Why would I want to install fastthread? Thanks, Joe

Hello Everyone, We''re hard at work getting the hot new win32 service Luis wrote out and ready for production. We''re hoping to have that included in the 1.0 RC1 release we make very soon. This pre-release is just to make sure that we didn''t step on any toes. Install it with: $ gem install fastthread --source=http://mongrel.rubyforge.org/releases $ gem install

With Mongrel 0.3.18, I have not seen a single one of the hangs that I have been grousing about for the past N weeks. Thanks MenTaLguY and Zed! Q: Mongrel loads fastthread, Mongrel loads Rails, Rails loads OCI8, OCI8 requires ''thread''. That means OCI8 is using fastthread too, right? Steve

I''m confused. Wasn''t threading fixed in 1.8.6, negating the need for fastthread? Why is fastthread still a requirement of Mongrel? Just curious. :)

Hi all, please help me: First time I totally had to delete all ruby and Rails because of this problem. How to solve it well? The message is: *Could not find gem ''sqlite3-ruby (>= 0, runtime)'' in any of the gem sources.* *Try running `bundle install`* I have *Ubuntu* Linux. ruby -v = *1.9.2p0* gem -v = *1.3.7* rails -v = error message again, 2 hours ago it was "rails

Hello Minions! It''s *finally* here. Mongrel 1.0 RC1 for everyone to test, even the win32 folks. I managed to get everything to build on windows, including fastthread, and even cleaned up the "releases source":http://mongrel.rubyforge.org/releases/ so that it should install cleaner. Win32 will have to try and report problems, as it seems rubygems is real finicky on win32.