On Jan 12, 2008 12:37 AM, Will Green <[EMAIL PROTECTED]> wrote: > Is nmake in your path? If so, from your comments, it appears that > *some* of your gem installs ARE compiling gems with whatever Platform > SDK you have installed (looks like its Server 2003). >
Oh, I think I overlooked at the comments done in this thread.. Yeah: if oyu have VC8/9 and Platform SDK in the Path, any gem that output "Building native extension" legend during installation will show up some serious problems. > Luis can explain far better than I, but gems compiled with VC 8 are NOT > compatible with the One Click installer (which is compiled with VC 6). > Sure, they *might* run, but they'll lead to trouble. > Yep. Exactly. 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. Anyway, if you had installed both VC8 and Platform SDK, you shouldn't see the missing runtime... unless you have some gem that wasn't compiled properly (which is possible). > I've found this to be the most stable mix (short of buying a > Mac or installing Linux). > A mac is expensive, and will not remove the whole pain of using Ruby... check some of the Leopard nightmares around the web ;-) HTH, -- 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
