From: "Cody" <cody1 AT ktsnet DOT com>
Newsgroups: comp.os.msdos.djgpp
References: <3bfc2f62 AT leia DOT ktsnet DOT com> <9ti43o$vvd$1 AT nntp9 DOT atl DOT mindspring DOT net>
Subject: Re: djgpp 3.0.2 problem?
Lines: 14
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
X-Original-NNTP-Posting-Host: 216-60-177-153.ktsnet.com
Message-ID: <3bffe9a6@leia.ktsnet.com>
Date: Sat, 24 Nov 2001 12:29:25 -0600
NNTP-Posting-Host: 216.60.177.225
X-Complaints-To: abuse AT swbell DOT net
X-Trace: nnrp3.sbc.net 1006626660 216.60.177.225 (Sat, 24 Nov 2001 12:31:00 CST)
NNTP-Posting-Date: Sat, 24 Nov 2001 12:31:00 CST
Organization: SBC Internet Services
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com


"Marp" <marp AT 0 DOT 0 DOT 0 DOT 0> wrote in message
news:9ti43o$vvd$1 AT nntp9 DOT atl DOT mindspring DOT net...
> This is a known problem when compiling allegro with optimization with gcc
> 3.0.2. The allegro people are aware of this. You have 3 choices:
>
> 1. do a non-optimized build
> 2. build it with an older version of gcc
> 3. wait until it is fixed
>
> BTW, what version of allegro were you trying to build?
The latest WIP of allegro (3.9.40).