Hmm, you're right, it seems that RubyInline is where it's blowing up, not ParseTree (though I suppose it's possible ParseTree may be a dud, I can't remember what rubygems does when it fails to compile). Are you able to install RubyInline?
I found this on installing RubyInline that may be of some assistance: http://thewebfellas.com/blog/2007/12/2/imagescience-and-rubyinline-on-windows I'm not a merb developer, nor a windows developer (I joined to find some help in integrating merb with spork), so sorry I can't be much more help to you. I personally install co-linux on all of my windows machines that use ruby. I've found that it runs much faster than the windows native version... with a few drawbacks such as not being able to have a windows process fire up a ruby process (could be prohibitive for IDE users). Tim On Wed, Jul 1, 2009 at 10:45 AM, will<[email protected]> wrote: > > Thanks Tim, > > I took a look see at that dependency. The current installed gem is: > > c:...> gem list parsetree -V > > *** LOCAL GEMS *** > > ParseTree (3.0.4, 3.0.3) > > I was looking at other threads on "Merb failing on Windows" back from > late 2008. I've beeHn checking through each of the issues. > > 1. One big issue was/is SQLite3 -- The default "how to" doesn't > need SQLite3. > 2. The other was commenting out ParseTree ... that hasn't fixed > much either, I can't actully > decide what ParseTree is doing anyway. Why does it need to > compile some C code? > 3. Various other things that once checked, don't make a difference. > 4. Putting SQLite in the PATH on Windows was promised as some > 'magic' > > So far none of the above tips from the other threads make an iota of > difference. > > I suspect the real problem is either > > (a) Buried in RubyInLine some issue or an environment variable that > I haven't set. > (b) A bug in the code passed to RubyInline for this option or > configuration parameter > (c) A configuration option that I do NOT need is breaking the > simple demo. > > I am HOPING someone out there has made Merb work on Windows/XP with no > big shake. I think so far, I've eliminated most of the items people > found beforehand on this topic. > > It is worth noting this issue pops up quite often and it may be to do > with compiler parameters. I not the output is highlighting deprecated > switches and such. > > Hope to hear back soon. > > ... Will > > > On Jul 1, 6:10 pm, Tim Harper <[email protected]> wrote: >> From the looks of the backtrace there, it's trying to install >> ParseTree (a gem which allows ruby to access the ruby's AST) >> >> On Wed, Jul 1, 2009 at 12:37 AM, will<[email protected]> wrote: >> >> > Merb wiki and followed the steps for "Generate your first app" >> >> > * http://wiki.merbivore.com/howto/gettingstarted/firstapp >> >> > I only got to step #2, step #3 failed in the same compile problem as >> > before (see below). So I don't get it? > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "merb" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/merb?hl=en -~----------~----~----~----~------~----~------~--~---
