Xref: news2.mv.net comp.lang.objective-c:1780 comp.os.msdos.djgpp:3667
Newsgroups: comp.lang.objective-c,comp.os.msdos.djgpp
From: jlemon AT netcom DOT com (Jonathan Lemon)
Subject: Re: Objective-C with djgpp v2.0
Message-ID: <jlemonDr1ywH.5Mx@netcom.com>
Organization: NETCOM On-line Communication Services (408 261-4700 guest)
References: <4mf66e$7u5 AT news DOT myriad DOT net> <jlemonDqw7zJ DOT Itu AT netcom DOT com> <nnvii9ea9e DOT fsf AT tindra DOT lysator DOT liu DOT se>
Date: Tue, 7 May 1996 20:43:28 GMT
Lines: 17
Sender: jlemon AT netcom22 DOT netcom DOT com
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

In article <nnvii9ea9e DOT fsf AT tindra DOT lysator DOT liu DOT se>,
Niels Möller <nisse AT lysator DOT liu DOT se> wrote:
>jlemon AT netcom DOT com (Jonathan Lemon) writes:
>
>> In article <4mf66e$7u5 AT news DOT myriad DOT net>,
>> Obj-C runtime.  I've reattached the patch below - you'll need to recompile
>> djgpp to update the compiler and then recompile libobjc.a to generate the
>> correct machine code.  I know that this fixes the problem on a 486 class
>> machine, I don't know if it will fix it on a 386.
>
>Does that patch apply to Linux x86 boxes too?

I assume so.  The machine that bit me was a Sequent Symmetry (SMP x86 platform)
and the root cause of the problem was simply bad assembly code was being 
generated.  I don't have a linux box here, so I can't test it.
--
Jonathan