From:	Shawn Hargreaves <Shawn AT talula DOT demon DOT co DOT uk>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Allegro & optimisations
Date:	Sun, 27 Apr 1997 16:27:14 +0100
Organization:	None
Distribution:	world
Message-ID:	<ZJBV1TASB3YzEwnL@talula.demon.co.uk>
References:	<01bc51df$2cdbf220$943863c3 AT default>
NNTP-Posting-Host:	talula.demon.co.uk
MIME-Version:	1.0
Lines:	24
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

Thomas Harte writes:
>       Are there any known optimisations with which Allegro does not work? I am
>using 2.2, and I installed the latest wip, but when I went to make it, it
>stopped with some error before doing anything, so I don't think that's
>applicable.

I'm willing to bet that in fact this is the problem: you are mixing one
version of liballeg.a with a different version of allegro.h. Delete
liballeg.a from your djgpp/lib/ directory and allegro.h from
djgpp/include/, re-run make in your Allegro 2.2 directory, and I suspect
the problem will go away...

Without optimisation gcc doesn't inline any functions, so you will get
the compiled copies of everything from liballeg.a. With optimisation
enabled, some functions will be inlined from allegro.h, and if these
don't match up with the precompiled versions (in particular because I
recently added several new routines to the virtual function tables), bad
things will happen :-)



--
Shawn Hargreaves - shawn AT talula DOT demon DOT co DOT uk - http://www.talula.demon.co.uk/
Beauty is a French phonetic corruption of a short cloth neck ornament.

- Raw text -