thanks for the feedback. Here's what I found works for me: # ruby 1.9.1 install OS X # download http://ftp.gnu.org/gnu/readline/readline-6.0.tar.gz ./confgure make sudo make install
# http://www.ruby-lang.org/en/downloads/ # download ruby-1.9.1-p243.tar.gz autoconf ./configure --prefix=/usr/local/ruby-191-p243 --with-readline-dir=/ usr/local --enable-pthread --enable-shared make sudo make install # check your PATH edit ~/.bash_profile add to end of file: export PATH=/usr/local/ruby-191-p243/bin:/usr/local/bin:$PATH # doing something more generic and having a symlink is also cool sudo gem update --system sudo gem install methopara sudo gem install merb --source http://edge.merbivore.com --source http://gems.rubyforge.org sudo gem install thin thanks, Jon On Aug 13, 4:58 am, Pavel Kunc <[email protected]> wrote: > On Aug 12, 9:47 pm, Jon Hancock <[email protected]> wrote: > > > > > > > cleaned up my system and built 1.9.1 again this time with readline 6 > > and the following config options: > > ./configure --with-readline-dir=/usr/local --program-suffix=191 -- > > enable-pthread --enable-shared > > > Now when I install merb, I get this error: > > > Installing ri documentation for merb-cache-1.0.12... > > ERROR: While executing gem ... (ArgumentError) > > unknown encoding name - undecided > > > It seems like this merb google group is a bit of a ghost town the last > > few weeks I've been checking it. > > Am I alone in trying to get merb running on OS X with ruby 1.9.1 > > cohabiting with ruby 1.8.6? Note: I"m not even sure its the > > cohabitation thats the problem. > > > thanks, Jon > > Well I don't use two versions of Ruby at one time. I've symlink to / > usr/local/ruby-1.9.1p243 -> /usr/local/ruby which makes switching from > one ruby to another quite simple. > > Honestly I didn't hit any of the problems you're describing. I'm using > edge merb. gem install merb --sourcehttp://edge.merbivore.com-- > sourcehttp://gems.rubyforge.org. As well there was an guide how to > install Merb on 1.9.1 in the group lately. Feel free to ping me on the > IRC (kupa). > > Pavel > > > > > On Aug 12, 4:15 pm, Jon Hancock <[email protected]> wrote: > > > > trying again...doing a cleanup first.> sudo gem191 uninstall merb-core > > > > Remove executables: > > > merb > > > > I answer Yes, it tells me it uninstalls. So I then check: > > > > > which merb > > > > /usr/bin/merb > > > > > which merb191 > > > > /usr/local/bin/merb191 > > > > seriously, how bad does this get? I have heard people telling merb is > > > working under 1.9.1. Seems pretty broke to me so far. > > > > On Aug 12, 3:29 pm, Jon Hancock <[email protected]> wrote: > > > > > I've installed ruby 1.9.1-p243 on OS X. Managed to get it coexisting > > > > with ruby 1.8.6 as near as I can tell. > > > > Then installed merb gems: > > > > sudo gem191 install methopara --format-executable > > > > sudo gem191 install merb --format-executable > > > > > I get these errors when running merb on a barebones project which > > > > works under 1.8.6: > > > > > > merb191 -a thin > > > > > /usr/local/lib/ruby191/gems/1.9.1/gems/merb-core-1.0.12/lib/merb-core/ > > > > dispatch/router/behavior.rb:18: warning: undefining `object_id' may > > > > cause serious problem > > > > /usr/local/lib/ruby191/gems/1.9.1/gems/merb-core-1.0.12/lib/merb-core/ > > > > dispatch/router/behavior.rb:18: warning: undefining `__send__' may > > > > cause serious problem > > > > > Any ideas? > > > > thanks, Jon --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
