Nicola Pero <nicola.pero <at> meta-innovation.com> writes: > > > I've did that many times. gnustep-make configure script tells me : > > > > checking for custom shared objc library... > > /c/GNUStep/System/Library/Libraries > > checking whether objc has thread support... yes: > > checking whether we should use native ObjC exceptions... no > > configure: Native objective-c exceptions were requested, but the compiler > > configure: doesn't support them. > > configure: error: compiler doesn't support native objective-c exceptions > > > > ... and configure fails. > > Oh ... I see. You are right - it's more complicated. > > Your problem is that the first time you configure gnustep-make, the new > libobjc is not yet installed, but gnustep-make will try compiling the ObjC > snippet to check if native exceptions actually work. That will fail, but > then you can't compile the new libobjc!
Everything becomes clear :-) But then i should not be the only one with this problem :-\ > Presumably we need a configure flag to force native-exceptions even if > the compiler would seem to fail when compiling them ? > (...) A working configure script in libobjc might be useful... Then enable-native-exceptions would be a libobjc option, no more a make one. Xavier _______________________________________________ Gnustep-dev mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnustep-dev
