Bug 87016 – dev-ruby/fxruby-1.2.4 (and all other versions of fxruby) force compile at -O0 for no apparent reason.

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description Ferris McCormick (RETIRED) 2005-03-28 12:17:59 UTC]

All versions of fxruby (ruby-fox interface) force the build to proceed at -O0.  Experience has shown me
that using the CFLAGS ruby passes in during the setup works fine.
(For me, that measn CFLAGS='-O2 -pipe -mcpu=ultrasparc' on sparc, but it depends on how ruby was built, of course.)

Compiling at -O0 results in huge, slow libraries and (in my opinion) is always wrong.

While we're at it, when I build FXruby by hand, I always use 'make -j2' with no problems, and it goes a lot faster for these huge c++ wrappers.
I understand that the build is controlled by install.rb, but a parallel make for the c++ portion would be a lot nicer.

[Comment 1 Ferris McCormick (RETIRED) 2005-03-28 12:53:32 UTC]

Created attachment 54712 [details, diff]
Patch to apply in dev-ruby/fxruby to let fxruby use ruby's CFLAGS instead of forcing -O0.

If in dev-ruby/fxruby you patch thus: patch -p0 -z- -b < fxruby-1.2.4.patch,
then fxruby will not
change the CFlAGS passed in by ruby to include -O0.  This results in much
longer compile times,
but smaller and faster fox interface for ruby.

[Comment 2 Ferris McCormick (RETIRED) 2005-03-28 12:54:46 UTC]

Tested with 1.2.4, but the same sort of thing applies to all versions of fxruby, really.

[Comment 3 Caleb Tennis (RETIRED) 2005-09-22 18:59:12 UTC]

ferris, please commit this patch if you're still up to it.

[Comment 4 Ferris McCormick (RETIRED) 2005-09-23 07:37:18 UTC]

(In reply to comment #3)
> ferris, please commit this patch if you're still up to it.

Done for fxruby-1.2.2, fxruby-1.2.6.  Update uses sed instead of a patch file,
mirroring the unpack function in 1.2.6.  Both versions build without forcing
'-O0', install, and run the examples correctly.  (Testing -1.2.6 requires some
package unmasking, of course.)

Notice that the example for textedit does not run with fxruby-1.2.xx, but this
appears to be because of a change in the UI for ruby/fox, and is independent of
this enhancement.