X-Authentication-Warning: new-smtp2.ihug.com.au: Host p103-tnt3.syd.ihug.com.au [203.173.132.103] claimed to be acceleron
Message-ID: <00a701c16f57$7dfee820$0a02a8c0@acceleron>
From: "Andrew Cottrell" <acottrel AT ihug DOT com DOT au>
To: "Andris Pavenis" <pavenis AT lanet DOT lv>
Cc: <djgpp-workers AT delorie DOT com>
References: <Pine DOT A41 DOT 4 DOT 05 DOT 10111171158190 DOT 58058-100000 AT ieva06>
Subject: Re: DJGPP & Windows 2000 / XP report for 17-Nov-2001
Date: Sat, 17 Nov 2001 22:02:59 +1100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Reply-To: djgpp-workers AT delorie DOT com

I have changed the line to now read:

   "GCC 3.02 does not work with Allegro. Please use GCC 2.9.5.3 if you are
using Allegro."

The link to the experimental version is still there. I slightly changed the
wording.

Is this okay?

Andrew

----- Original Message -----

From: "Andris Pavenis" <pavenis AT lanet DOT lv>
To: "Andrew Cottrell" <acottrel AT ihug DOT com DOT au>
Cc: <djgpp-workers AT delorie DOT com>
Sent: Saturday, November 17, 2001 9:07 PM
Subject: Re: DJGPP & Windows 2000 / XP report for 17-Nov-2001


>
>
> On Sat, 17 Nov 2001, Andrew Cottrell wrote:
>
> > The following is the main change that are included since the last
report:
> >     1) GCC 3.02 now available for download. (If using Allegro do not use
> > 3.02, wait for GCC 3.03 release)
>
> I save following line on clio.rice.edu:
>
> GCC 3.02 does not work with Allegro. GCC 3.03 does, but it is not out yet
> for DJGPP. In the mean time use GCC 2.9.5.3.
>
> My comments:
>
> gcc-3.0.3 is not out at all not only for DJGPP. It's a patched prerelease
> (read CVS snapshot of gcc-3_0-branch) version I made available which fixes
> this problem
>
> The bug which causes problem with src/unicode.c in Allegro is not fixed
> in GCC CVS repository at all yet (neither in gcc-3_0-branch nor in trunk).
>
>
>
> Anyway I think I'll include this patch in next update of gcc-3.0.X for
> DJGPP even if it will not be in CVS (I think that poeple reporting PR#4529
> again and again annoys enough to get fix in after not so long time)
>
> Andris
>
>
>
>