On 20 February 2010 19:34, Steven G. Harms wrote:
>
> 1. I do a lot of experimentation with Ruby, and as such the default
> Ruby.framework solution "helpfully" provided by Apple kept getting in
> the way. Therefore, it is gone. Furthermore, something of appeal to
> me lately is to have everything gathered from the net and installed on
> my machine to be done in a nice, neat, orderly fashion: into /usr/
> local the way we used to do on Unices.
>
> 2. Data to support this:
>
> stha...@stharms-mac:/usr/local/src/vim7$ ls -l /System/Library/
> Frameworks/RubyCocoa.framework/
> stha...@stharms-mac:/usr/local/src/vim7$ which ruby
> /usr/bin/ruby
> stha...@stharms-mac:/usr/local/src/vim7$ ls -l /usr/bin/ruby
> lrwxr-xr-x 1 root wheel 19 Jan 20 04:17 /usr/bin/ruby -> /usr/local/
> bin/ruby
> stha...@stharms-mac:/usr/local/src/vim7$ ls -l /usr/local/bin/ruby
> -rwxr-xr-x 1 root wheel 8976 Jan 19 21:12 /usr/local/bin/ruby
> stha...@stharms-mac:/usr/local/src/vim7$ !$ --version
> /usr/local/bin/ruby --version
> ruby 1.8.7 (2009-12-24 patchlevel 248) [i686-darwin10.2.0]
>
> 3. This leads me to ask, is there a way to have --enable-rubyinterp
> respect my custom Ruby installdir?
The problem is that the configure file expects there to be a
Ruby.framework on your computer -- installing a plain non-framework of
Ruby requires the Ruby header files to be included differently. You
can work around this manually as follows:
1. open src/if_ruby.h
2. edit the line which says
#include <Ruby/ruby.h>
to say
#include <ruby.h>
3. make
It would be possible to rewrite the configure script to allow for a
missing Ruby.framework, but I must say that it really is not a good
idea to delete things from subfolders of /System so it's not something
I want to encourage. For now, I'll leave things as they are: if more
people face this problem I may reconsider my stance and modify the
configure script.
Björn
--
You received this message from the "vim_mac" maillist.
For more information, visit http://www.vim.org/maillist.php
