From: pavenis AT lanet DOT lv
To: "Eric Botcazou" <ebotcazou AT libertysurf DOT fr>, djgpp AT delorie DOT com
Date: Wed, 14 Nov 2001 15:09:27 +0200
MIME-Version: 1.0
Subject: Re: Allegro compilation error
Message-ID: <3BF28927.7169.1005F4B@localhost>
In-reply-to: <9stg9p$2fet$1@news5.isdnet.net>
X-mailer: Pegasus Mail for Windows (v4.01)
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Content-description: Mail message body
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 14 Nov 2001 at 11:16, Eric Botcazou wrote:

> > Compiling Allegro for djgpp, optimised. Please wait...
> > tools/dat2s.exe -p setup -o obj/djgpp/setupdat.s setup/setup.dat
> > Exiting due to signal SIGSEGV
> 
> You're compiling with gcc 3.0.2, aren't you ?
> This is a known problem due to gcc 3.0.2; note that another problem prevents
> the optimized version of the library from working.
> 

It is known bug in gcc-3.0.X (and also current development tree of 
gcc). gcc-3.0.2 miscompiles src/unicode.c from allegro-3.9.3* when 
command line option -fomit-frame-pointer is being used. 

The fix for this problem is known

	http://gcc.gnu.org/ml/gcc-patches/2001-11/msg00698.html

but is not yet even in CVS version of gcc. 

So we could expect that this bug will be fixed in next update of 
DJGPP port of gcc-3.0.X.

Andris