From: John Joyce <dangerwillrobinsondanger@...>
Date: 2008-03-23T02:50:10+09:00
Subject: Re: XCode, Mac OS X, Ruby C Extension


On Mar 22, 2008, at 8:10 AM, Wladjmir Wlj wrote:

> Hi,
>
> i 've a problem trying to compile a simple C Extension, that  
> actually do
> nothing, only print an hello message.
> If from XCode i create and build a new Ruby C Extension, then i try to
> recall it from a ruby script, that use the ruby interpreter compiled
> from MacPort , a BUS ERROR is returned, au contraire, if i use the
> Leopard's ruby interpreter, it works.
> Already tried to change the XCode project target properties to 32 and
> 64bit but no way to work with that ,and i do non understand why, 2  
> ruby
> interpreters can't use the same c extension.
>
> Thanks
> -- 
> Posted via http://www.ruby-forum.com/.
>
Since the built-in Leopard build of Ruby is the future for OS X, I  
would recommend focusing your efforts there. (and maybe 1.9...)
Clearly, at this time, Apple is taking Ruby pretty seriously.  
MacPorts can introduce additional complexities to the situation. If  
you still want to get it working, by all means, do it. I'm just  
saying that the future of a stable, predictable OS X Ruby  
distribution is likely to be the one that is bundled.
On the other hand, if you have older Macs you need to support that  
does not fix things, does it?

Let's just hope the MS and Mac versions of Ruby don't diverge too  
much... (beyond their native Frameworks of course)