On 3/19/07, Michael Gardner [EMAIL PROTECTED] wrote:
Also, regarding the problem configuring gnustep-make with
--enable-native-objc-exceptions: I emailed the port's maintainer, and
he mentioned that he got the same result on his FreeBSD system. It
looks like a gcc bug to me, but can anyone
That's brilliant ... I added --shared-libgcc (on all platforms) to the
linking stage when native ObjC exceptions are enabled. :-)
Hopefully that fixes it ... Michael, any chances you could try it out with
gnustep-make from trunk to see if it's fixed now ? :-)
That might be difficult since
Thanks for the tips. I just installed GNUstep from trunk, and can
confirm that the problem is fixed. :)
-Michael
On 3/19/07, Nicola Pero [EMAIL PROTECTED] wrote:
That's brilliant ... I added --shared-libgcc (on all platforms) to the
linking stage when native ObjC exceptions are enabled. :-)
: Crash with new-style exceptions on FreeBSD amd64
On 3/15/07, Andrew Pinski [EMAIL PROTECTED] wrote:
On 3/15/07, Michael Gardner [EMAIL PROTECTED] wrote:
That bug's description doesn't seem to match the symptoms I'm seeing,
and it's reported against gcc 4.3 rather than 4.1.
For one
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
On 3/15/07, Richard Frith-Macdonald [EMAIL PROTECTED] wrote:
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
D'oh! I forgot to attach config.log, after I accidentally reloaded the
window in which I was writing the previous email and had to re-type
the whole thing. Sorry about the noise.
-Michael
On 3/15/07, Michael Gardner [EMAIL PROTECTED] wrote:
On 3/15/07, Richard Frith-Macdonald [EMAIL PROTECTED]
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.
I believe that Andrew is
Andrew -- do we need to add -fexceptions on all platforms or only on some ?
Well, I added it to all platforms on gnustep-make trunk. :-)
If anyone has got a FreeBSD (or any other non-GNU/Linux platform) and is around
to help
a little, you could try gnustep-make from trunk, using
./configure
On 3/15/07, Nicola Pero [EMAIL PROTECTED] wrote:
I believe that Andrew is suggesting trying
-fobjc-exceptions -fexceptions
both when compiling and linking. Can you try it out ?
Ah, I misread; sorry about that. I just tried that suggestion:
gcc41 -c -fobjc-exceptions -fexceptions
On 3/15/07, Richard Frith-Macdonald [EMAIL PROTECTED] wrote:
I thought that compiling with '-x objective-c' was supposed to have
the same effect as compiling a file with a .m extension too.
If that understanding is correct, I don't see how the behavior you
are seeing could be anything other than
On 3/15/07, Andrew Pinski [EMAIL PROTECTED] wrote:
On 3/15/07, Richard Frith-Macdonald [EMAIL PROTECTED] wrote:
I thought that compiling with '-x objective-c' was supposed to have
the same effect as compiling a file with a .m extension too.
If that understanding is correct, I don't see how
On 3/15/07, Michael Gardner [EMAIL PROTECTED] wrote:
On 3/15/07, Andrew Pinski [EMAIL PROTECTED] wrote:
On 3/15/07, Richard Frith-Macdonald [EMAIL PROTECTED] wrote:
I thought that compiling with '-x objective-c' was supposed to have
the same effect as compiling a file with a .m extension
On 3/15/07, Andrew Pinski [EMAIL PROTECTED] wrote:
On 3/15/07, Michael Gardner [EMAIL PROTECTED] wrote:
That bug's description doesn't seem to match the symptoms I'm seeing,
and it's reported against gcc 4.3 rather than 4.1.
For one, it is the same symptom, in that we are not linking against
I'm having problems using new-style exceptions with GNUstep on
FreeBSD 6.2 (amd64). I have the following program (main.m):
#include Foundation/Foundation.h
int main(int argc, char ** argv) {
@try {
@throw nil;
} @catch (id thing) {
printf(caught!\n);
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Helge Hess wrote:
On Mar 14, 2007, at 21:46, Michael Gardner wrote:
I'm having problems using new-style exceptions with GNUstep on
FreeBSD 6.2 (amd64).
Does GNUstep support @throw, @catch??
Thanks,
Helge
Yes, for almost two years
[EMAIL PROTECTED]
Sent: Wed, March 14, 2007 9:46 pm
To: gnustep-dev@gnu.org
Subject: Crash with new-style exceptions on FreeBSD amd64
I'm having problems using new-style exceptions with GNUstep on
FreeBSD 6.2 (amd64). I have the following program (main.m):
#include Foundation/Foundation.h
int main
:46 pm
To: gnustep-dev@gnu.org
Subject: Crash with new-style exceptions on FreeBSD amd64
I'm having problems using new-style exceptions with GNUstep on
FreeBSD 6.2 (amd64). I have the following program (main.m):
#include Foundation/Foundation.h
int main(int argc, char ** argv) {
@try
18 matches
Mail list logo
