[Fxruby-users] Re: How to build FXRuby on Mac OS X (was: Mac OS X)

[Lyle J. <ly...@kn...>]

On Feb 6, 2004, at 5:08 PM, Gabriel Pack wrote:

> I'm sorry to bug everyone if this has already been covered before; but  
> I'm new, and I would really like to get FreeRIDE running on Mac OS X  
> Panther (10.3.2).
>
> I've tried to make sense of the instructions here  
> (http://rwiki.jin.gr.jp/cgi-bin/rw-cgi.rb?cmd=view; 
> name=FreeRIDE+on+X11+for+Mac+OS+X), but I'm missing something.   
> Basically, when I try to test my installation of the FXRuby extension  
> using irb, I get the following:
>
> irb(main):001:0> require 'fox'
> dyld: ruby Undefined symbols:
> __ZTVN10__cxxabiv117__class_type_infoE
> __ZTVN10__cxxabiv120__si_class_type_infoE
> ___gxx_personality_v0
> Trace/BPT trap
>
> Can anyone offer any help?

I have gotten it to work using the following recipe, but I don't yet  
understand why it works. So take that for what you will ;)

Anyways, the trick has to do with building the FOX library itself.  
First, set the CPPFLAGS and LDFLAGS environment variables as necessary  
to pick up the header files and libraries for optional things like the  
PNG libraries and such. For example, since I'm using fink, those things  
are installed under /sw:

	setenv CPPFLAGS -I/sw/include
	setenv LDFLAGS -L/sw/lib

Next, configure FOX as usual, e.g.

	./configure --prefix=/sw --with-opengl=opengl

Now here's the tricky part. As a side effect of the configure step, you  
should now have a shell script named "libtool" in the fox-1.0.x  
subdirectory. You need to replace this automatically generated version  
with this patched version:

	http://www.knology.net/~lyle/libtool.gz

There's basically one line's difference between this one and the one  
that "configure" produces, and I'm still not clear on the significance  
of that difference -- other than it makes FXRuby work properly. Once  
you've replaced this "libtool", go ahead and build & install FOX as  
usual:

	make
	sudo make install

Now, build FXRuby following the normal instructions and all should be  
well.

Yes, some day real soon now I'm going to do my homework and figure out  
why that change in the libtool script fixes things. If you already know  
the answer, that's even better ;)

Hope this helps,

Lyle