From:	Andrew Cottrell <andnews AT ihug DOT com DOT oz DOT au>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Builiding Allegro
Date:	Sat, 19 Apr 2003 09:47:01 +1000
Organization:	ECLiPSE
Lines:	26
Message-ID:	<a431avsr447df2ujr61ba715f83a2scfcu@4ax.com>
References:	<Xns9361F1524DECEraf256com AT 213 DOT 180 DOT 128 DOT 20>
NNTP-Posting-Host:	203-173-153-63.ihug.net
Mime-Version:	1.0
X-Trace:	lust.ihug.co.nz 1050709622 9073 203.173.153.63 (18 Apr 2003 23:47:02 GMT)
X-Complaints-To:	abuse AT ihug DOT co DOT nz
NNTP-Posting-Date:	Fri, 18 Apr 2003 23:47:02 +0000 (UTC)
X-Newsreader:	Forte Agent 1.92/32.572
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

>I just downloaded all newest files for DJGPP (and Allegro from Djgpp's zip-picker).
>
>But i can't make allegro :(
>
>I write a .bat that calls 2 bat's
>fix djgpp
>make allegro

What does "fix djgpp" do as Allegro builds without problems if you
have the correct Allegro and GCC versions. Ie GCC 3.x needs Allegro
4.y. 

Why do you need to specify "make allegro" to build Allegro? Allegro
builds fine with just "make".

The errors look like you are not linking in liballeg.a .

I suggest that you :-
1) grab the Allegro 4.03 RC2 from http://alleg.sourceforge.net/ as
this has a number of fixes that you may want. 
2) Build it using "make" to ensure that it does work
3) Modify the batch file to ensure that is uses "call fix.bat djgpp"
if fix is  a bat file as you need to add the command "call" before
executing another batch file within the master batch file.

Andrew

- Raw text -