John Koleszar writes:
> No hurry.. Like I said, there's a workaround. Wanted to get it out there
> on this list in case it comes up in swig-user or something. Most people
> probably don't bother trying to turn optimizations on for these bindings
Umm. Actually this may not necessarily be true because there sometimes
the C flags might come from non-obvious places.
Recently I figured out how to get Perl's Module::Build working for
swig. And what happens by default in C compilation is that the CC
flags are picked up by whatever was used to build Perl. Guess what, I
ran into that bug too because Perl (from an RPM) used optimization. I
hadn't tracked things down though to -fno-strict-antialiasing, but
rather than turned off all optimization. And the problem is not
strictly a Module::Build problem since when I was using autotools I
was in effect doing the same thing.
Building any extension for Perl is going to require one to get Perl's
cflags - which may include optimization.