Date: Thu, 22 Nov 2001 08:35:14 +0200 (WET)
From: Andris Pavenis <pavenis AT lanet DOT lv>
X-Sender: pavenis AT ieva06
To: Marp <marp AT 0 DOT 0 DOT 0 DOT 0>
Cc: djgpp AT delorie DOT com
Subject: Re: djgpp 3.0.2 problem?
In-Reply-To: <9ti43o$vvd$1@nntp9.atl.mindspring.net>
Message-ID: <Pine.A41.4.05.10111220832370.22820-100000@ieva06>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk



On Thu, 22 Nov 2001, Marp wrote:

> 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

Get update of DJGPP port of gcc-3.0.2. I put fix from gcc-3_0-branch for 
-fomit-frame-pointer problems there. But be carefull - some mirrors
may still have old version

Andris