> 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! ;-) Interesting chicken-and-egg problem. Presumably we need a configure flag to force native-exceptions even if the compiler would seem to fail when compiling them ? Then you'd do cd core/make ./configure --enable-native-exceptions-even-if-they-seem-not-to-work make install cd ../../dev-libs/libobjc make make install cd ../../core/make ./configure --enable-native-exceptions make install Hmmm. Thanks _______________________________________________ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
