From: Luis Lavena <luislavena@...>
Date: 2007-12-20T11:54:59+09:00
Subject: Re: gems that won't install mswin32

On Dec 19, 11:19 pm, "Jack Johnson" <jjohn...@cyberworlds.com> wrote:
> [...]
>
> Hi, Luis -
>
> Thanks for taking the time to reply. I have searched on the topic, and
> posted on parts of it before, but the fact that I (and others) have had the
> same issues with rubygems 0.9.4 seems to always get lost along the way. I
> was unable to install fastthread etc. with 0.9.4 because of the same issue -
> it always wanted to compile. I'm mostly unfamiliar with ruby, so I was
> hoping I was just missing something obvious that would allow things to work
> again as they used to. I guess I'll just quietly wait for that magic to
> happen in some future release.
>

Jack, I must apologize,

I did further investigated the issue regarding RubyGems 0.9.5,
Mongrel, fastthread and other gems:

- RubyGems trunk how have the required fixes to properly install and
handle the current gems.

That means no more wrong compilation of mongrel and associated gems
(fastthread)

- Fastthread gem (mswin32 one) bundles the pre-compiled extension, but
by mistake (MY MISTAKE), I missed removing the ext/extconf.rb part of
it, and rubygems try to compile it every time.

I'm fixing it right now and waiting to hear back from Tom Copland
about replacing the current gem on rubyforge.

Sorry if my previous post sounds harsh, but this was asked a lot of
times in the list, also raised in the RubyonRails blog and some other
posts around the web describe the problem.

This is my blog post (first english post) about this:

http://blog.mmediasys.com/2007/12/19/latest-rubygems-and-rails-is-a-deadly-combo/

Regards and please excuse the sound of my previous reply.