Message-ID: <8D53104ECD0CD211AF4000A0C9D60AE3015DAC84@probe-2.acclaim-euro.net>
From: Shawn Hargreaves <ShawnH AT Probe DOT co DOT uk>
To: Andris Pavenis <pavenis AT lanet DOT lv>
Cc: djgpp AT delorie DOT com
Subject: RE: Scratch that, installing allegro
Date: Tue, 31 Aug 1999 15:13:00 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.0.1460.8)
Content-Type: text/plain
Reply-To: djgpp AT delorie DOT com

Andris Pavenis writes:
>> It would, however, be nice to fix up the 3.11 version that is currently 
>> on Simtel to make it work with gcc 2.95.
>
> I'm including my patch below. It cowers not only problems I met with
> gcc-2.95 but also other one with recent development snapshot of binutils
> (should not break earlier versions).

I actually just uploaded a patch to DJ that fixes the gcc 2.95 problems
(I was getting very bored with the flood of "can't compile it" posts :-)
But I didn't know about this binutils issue: is that another one that
causes compile errors, and if so, where can I get a copy of these binutils
to check it out?

Actually, I'm pretty sure that these problems have already been fixed in 
the development version of Allegro (we had a bunch of problems with 
Mingw32 needing to use "call *%reg" instead of just "call %reg", and
with a few wrong size suffixes), but we are still quite a way short of
calling that code an official release, so if this is going to become
a problem in the near future, I should make another patch to the existing
version.


	Shawn Hargreaves.