X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
From: Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Building ALLEGRO libraries
Date: 6 Apr 2006 08:53:18 GMT
Lines: 22
Message-ID: <49k37uFovesfU4@news.dfncis.de>
References: <BAY16-F19296421CD9756FA69554FE7C80 AT phx DOT gbl>
X-Trace: news.dfncis.de iihbkEtH8odL8XD9mzzIywks2bL4l/TaBRsvT/x6hsn3aj3dYiQV7AR7XD
X-Orig-Path: not-for-mail
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

cinzia genuini <cinzia DOT gen AT hotmail DOT it> wrote:
> While I MAKE Allegro I receive  these messages when the COMPILER reaches
> file FLI.C:
> in function _fli_read_header INVALID LVALUE IN INCREMENT,
> in function _fli_read_frame INVALID LVALUE IN INCREMENT,
> in function _fli_parse_chunk  INVALID LVALUE IN INCREMENT.

You should bring this to the attention of the Allegro maintainers.  I
don't think the DJGPP group is thte place for doing that.  And when
you do, please state exact versions of GCC and Allegro you observed
that in.

> In addition there is the WARNING:
> MCPU deprecated use MTUNE or MARCH instead. 

That one's easy --- the Allegro you're trying to compile is older than
the compiler, and therefore its makefile is somewhat outdated.  Fix it
if you can, or get the Allegro guys to fix it.

-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.