On 15 Mar 2007, at 06:20, Michael Gardner wrote:
On 3/15/07, Andrew Pinski <[EMAIL PROTECTED]> wrote:
You still have to compile your program with -fexceptions to get
"objc"
exceptions working with objective-C.
But that doesn't explain (2), where I *do* use -fobjc-exceptions, only
with gcc instead of g++, and with a separate linking step instead of
all-at-once. That's what gmake is doing, which is why I want to
understand what's going on here.
Oh, and another interesting tidbit: I noticed in
$GNUSTEP_SYSTEM_ROOT/Library/Makefiles/config.make the following line:
USE_OBJC_EXCEPTIONS = no
I don't know why that was set that way by default, but changing it to
"yes" (followed by re-sourcing GNUstep.sh and re-compiling my program)
had no effect. In any case it wouldn't seem to explain why I don't get
the crash if I do the compilation and linking in a single step, or if
I use g++ instead of gcc.
Presumably you failed to use the --enable-native-objc-exceptions when
configuring gnustep-make.
It's hardly surprising that the wrong flags are being passed to the
compiler and the wrong config options being set if the system was not
configured to use native exceptions.
_______________________________________________
Gnustep-dev mailing list
Gnustep-dev@gnu.org
http://lists.gnu.org/mailman/listinfo/gnustep-dev
