On 9 Jan 2009, at 22:08, Larry Campbell wrote:
Had another go at this, with gnustep-make 2.0.8 and both gnustep-
base 1.18.0 and 1.19.0, with the same result. So sad. I was tempted
by the comment:
1.2 Noteworthy changes in version `1.19.0'
==========================================
* Support for native objective-c exceptions
This is with gcc 4.1.2. Has anyone else ever tried this
successfully? Did you have to use a different version of gcc?
I use native objc exceptions with gcc-4.4.0. However, if you want the
uncaught exception handler to work, you need to have patched the
runtime.
- lc
On Dec 26, 2007, at 7:22 PM, Larry Campbell wrote:
Before I spend a lot of time figuring out how to fix this, I
thought I'd ping the list to see if anyone else has run into this.
I just tried turning on native Objective-C exceptions (--enable-
native-objc-exceptions to gnustep-base/configure). Everything seems
to build OK, but if there are any Objective-C++ modules that use
exceptions in my link, the link fails with:
undefined reference to `typeinfo for NSException*'
As long as there's no Objective-C++ (.mm) in the link, I'm fine.
This happens with both (gnustep-make 1.13.0 + gnustep-base 1.13.1)
and (gnustep-make 2.0.2 + gnustep-base 1.14.1). I tried renaming
NSException.m to NSException.mm (and fixing the type errors the
stricter compile revealed); no joy.
Has anyone already run into this (and, hopefully, fixed it)?
I don't use C++, so I haven't run into this ... it's possible that
there is an incompatibility between the exception support in the C++
and Objective-C runtime libraries provided by gcc.
_______________________________________________
Discuss-gnustep mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/discuss-gnustep
