On Jan 12, 2008 3:48 PM, Wes Gamble <[EMAIL PROTECTED]> wrote: > > I'll suggest you install a clean version of One-Click Installer > > (latest is 1.8.6-26) and then install your gems in a clean > > environment. > > > > Ensure first you don't have nmake or cl in your path. That will avoid > > gems being compiled with VC8. > > > > This is kind of funny, because when rubygems 0.9.5 came out, it appeared > that I was now _required_ to compile native gems on Windows and that is > when I finally made sure that nmake would work to completion and > actually compile stuff. It sounds like you're saying that I should have > waited for the pre-compiled gems to get fixed :). >
Oh, no! Please try upgrading rubygems to 1.0.1!!! 0.9.5 is broken for us (Windows users)! I posted this a way back when Rails guys did the 2.dot Oh release: http://blog.mmediasys.com/2007/12/19/latest-rubygems-and-rails-is-a-deadly-combo/ I worked a few hours with Eric Hodel getting this fixed before rubygems 1.0... Please, update to it and the pain will go away :-D > > A mac is expensive, and will not remove the whole pain of using > > Ruby... check some of the Leopard nightmares around the web ;-) > > It's true. But given that, in my experience, many gem and plugin > developers test little to not at all on Windows, the Mac is the > "platform of least surprise". Although I've been able to solve all of > my Windows-specific Ruby issues eventually, I am just tired of having to > spend time and energy doing that. > "of least surprise" ... right :-) I also like the "think different" motto and the just offer 2 (or one) option to "be different". If you don't do it "the mac way", then you should die... :-P -- Luis Lavena Multimedia systems - A common mistake that people make when trying to design something completely foolproof is to underestimate the ingenuity of complete fools. Douglas Adams _______________________________________________ Mongrel-users mailing list Mongrel-users@rubyforge.org http://rubyforge.org/mailman/listinfo/mongrel-users
