Which OS X Tiger PPC C compiler is best to use for Ruby?

I have recently started picking up Ruby again on my OSX PowerPC
system. I use MacPorts to build stuff like PostgreSQL and other
“system” components, and then like to build different versions of
Ruby under /usr/local/ruby-1.8.6-p111/… so that I can have multiple
versions.

I had been using Apple’s 4.0 gcc and getting occasional errors with
rdoc documentation installs terminating my build. It seems that if I
do a gcc_select 3.3 before the build then everything proceeds just
fine to completion with no problems. This might explain some of the
comments like “Some readers also report seeing an RDoc failure error.
This one is actually nothing to worry about. Just re-run the original
command above, or don’t. Things should be fine either way (really).”
on Dan Benjamin
ruby_rails_lighttpd_mysql_tiger?status=301

I have had a quick look around using common search engines, and I
haven’t seen any list of recommended or known bad combinations of gcc
and ruby on OSX. Does such a list exist? Should I invest the time
in compiling MacPorts’ gcc42?

I realise that this may become moot when Leopard ships (and mabe if
I’m allowed to buy a spiffy new Intel based Mac.)

Michael

Mike S. [email protected]
http://www.stok.ca/~mike/

The “`Stok’ disclaimers” apply.

Mike S. wrote:

actually nothing to worry about. Just re-run the original command above,
allowed to buy a spiffy new Intel based Mac.)

Michael

Hmmm…I’m using gcc 4.0.1 on my 15" Powerbook and I’ve never had a
problem with RDoc. My most recent build of Ruby was p110.

On Oct 14, 2007, at 16:40 , Mike S. wrote:

of the comments like "Some readers also report seeing an RDoc
I realise that this may become moot when Leopard ships (and mabe if
I’m allowed to buy a spiffy new Intel based Mac.)

You just need to rebuild your ruby. There’s a bug with -fschedule-
insns2, which is included with -O2. I don’t know where the bug lies,
though.

CFLAGS=-fno-schedule-insns2 ./configure
make clean && make && sudo make install

On 14-Oct-07, at 8:31 PM, Eric H. wrote:

proceeds just fine to completion with no problems. This might

I realise that this may become moot when Leopard ships (and mabe
if I’m allowed to buy a spiffy new Intel based Mac.)

You just need to rebuild your ruby. There’s a bug with -fschedule-
insns2, which is included with -O2. I don’t know where the bug
lies, though.

CFLAGS=-fno-schedule-insns2 ./configure
make clean && make && sudo make install

Thanks. I will give that a try!

Mike

Mike S. [email protected]
http://www.stok.ca/~mike/

The “`Stok’ disclaimers” apply.