Xref:	news2.mv.net comp.lang.objective-c:1752 comp.os.msdos.djgpp:3461
From:	luke-adamson AT tamu DOT edu (Luke Adamson)
Newsgroups:	comp.lang.objective-c,comp.os.msdos.djgpp
Subject:	Objective-C with djgpp v2.0
Date:	4 May 1996 08:57:50 GMT
Organization:	DigiPhone Corporation, Bryan/College Station Texas 409-693-8885
Lines:	36
Message-ID:	<4mf66e$7u5@news.myriad.net>
NNTP-Posting-Host:	toxin.myriad.net
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

Hello all,

I've fallen victim to the evil SIGFPE problem using Objective-C and dgjpp.  
So far, everyone I know using ObjC and djgpp is incurring the same 
difficulty.

Essentially, djgpp compiles my grok.m without errors or warnings (the file 
consists of one class, with one - sayHello method, very simple) but when run 
the executable, it gives:

Exiting due to signal SIGFPE
Coprocessor not available at eip=000021c9
[lots of fun ebx ecx, etc, fun.]
..
..
..

I'm not sure if others using Objective C, and djgpp are experiencing the 
`Coprocessor not available' error, but that SIGFPE problem has been popping 
up with regularity.

I'm running this on a 386SL.. using the provided fp emulation package.  I 
know the error also occurs on some 486's.

I _thought_ I saw someone on comp.lang.objective-c post some sort of patch to 
gcc 2.7.2, involving poor handling of some Objective-C issue, but I can't 
find the post, and the archive is unavailable, so for all I know, I might 
have dreamed it.

Does anyone know what the deal is?  Is _anyone_ out there making Objective-C 
and djgpp v2.0 working together happily?

(please cc: responses to luke-adamson AT tamu DOT edu, as I'm not able to read 
Usenet news often, thanks!)

	Luke

- Raw text -