Hi Richard,
Richard Frith-Macdonald wrote:
So the default is for gnustep-make to use native exceptions, but you can
override it using --disable-native-objc-exceptions, and you may need to be
aware that, if the compiler/runtime gnustep-base sees at configure time does
not support native exceptions, then the base configure process may override the
setting from when you configured make. I don't think there should ever be a
problem if you configure gnustep-make to use traditional setjmp based
exceptions though.
NB. make sure you have a clean instuall when changing this stuff ... if you
have some libraries/code built one way and some libraries/code built the other
way then you will get problems.
(I do know I need to recompile everything when switching)
sorry I missed that option :( but actually it doesn't help: I already
had "make" going standard while base native. I hoped forcing would help
though and I tried.
I configured and installed make with this:
./configure --prefix=/ --with-layout=gnustep
--disable-native-objc-exceptions
then I configure base and I explictely see during configure:
checking for non-fragile-abi support... yes
checking for objc_setUncaughtExceptionHandler() in runtime... no
checking for objc_set_unexpected() in runtime... no
checking for _objc_unexpected_exception in runtime... yes
checking whether to enable native Objective-C exceptions... no
checking for objc_sync_enter... (cached) yes
checking for thread-safe +initialize in runtime... yes
yet then build gives the previously copied mismatch error
../../Headers/Foundation/NSException.h:48:2: error: "gnustep-base is
configured
to use 'traditional' exceptions, but you are building for 'native'
exceptions."
but how?? maybe there is some trick missing... or configure doesn't
"force" clang
I got around with this:
./configure OBJCFLAGS=-fno-objc-exceptions
but this is inconvenient if I have to add it to every thing I need to
configure/compile. Do you think we can do this automatic with gnustep
make? or maybe we already have some wizardy but it isn ot working?
Riccardo
_______________________________________________
Gnustep-dev mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/gnustep-dev
