Both your problems will solve using proper version for Ruby 1.9.x. Merb 1.0.x is NOT Ruby 1.9.x compatible use Merb 1.1.0.pre gems.
Pavel On Mar 2, 6:46 pm, Michishige Kaito <[email protected]> wrote: > While at it, I was also getting these: > > /usr/lib/ruby/gems/1.9.1/gems/merb-core-1.0.15/lib/merb-core/dispatch/route > r/behavior.rb:18: > warning: undefining `object_id' may cause serious problem > /usr/lib/ruby/gems/1.9.1/gems/merb-core-1.0.15/lib/merb-core/dispatch/route > r/behavior.rb:18: > warning: undefining `__send__' may cause serious problem > > Maybe someone is interested and wants to fix it. I don't know enough about > merb internals. > > 2010/3/2 Michishige Kaito <[email protected]> > > > > > As stated above: > > > /usr/lib/ruby/site_ruby/1.9.1/rubygems/version.rb:186:in `strip!': can't > > modify frozen string (RuntimeError) > > > This is caused > > because > > /usr/lib/ruby/gems/1.9.1/gems/merb-core-1.0.15/lib/merb-core/bootloader.rb: > > 454:in > > `new' calls Gem::Version.new(RUBY_VERSION), where RUBY_VERSION seems to be a > > frozen string. #new calls #strip! on the frozen string, causing the > > RuntimeError. > > > Editing version.rb seemed way too hacky, so I edited merb's bootloader.rb > > to pass a dup of RUBY_VERSION instead. > > > Although, this is probably a bug with either ruby itself, or rubygems. -- 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.
