On Dec 29, 2:09 am, Carl Lerche <[email protected]> wrote: > hey there, I'm confusd by what you mean by "Our > code works fine on the first two but not on the third."
Our merb app passes all its model specs on all three platforms. However on Fedora, the routes don't compile. > There is a known issue (that I need to get submitted asap), but it > shouldn't appear until there are rough 2,000 routes defined. Also, > what does yacc have to do with all this? I haven't seen that before. > If it blows up at line 245, you must have a very small stack. We have under 50 routes defined. No route is particularly troublesome. In fact when I comment out enough of the routes (no matter which ones) it compiles.. seems 15 simple routes is all it can take before it pukes. I have no idea where yacc is getting involved.. I don't even have a command-line yacc/bison installed on the Fedora box. Is this something internal to the ruby libraries? > Could you provide more information? I'm curious about the setup. > Maybe try running ruby --version. ruby 1.8.6 (2008-08-11 patchlevel 287) [i386-linux] Thanks, Gary --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
