From: zargon AT hotmail DOT vom (Zargon)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Q: allegro_message
Organization: Zargon and Zed Take Over The Universe
Message-ID: <39412d39.31864646@news.globalserve.net>
References: <39402637 DOT 409213505 AT news DOT globalserve DOT net> <MPG DOT 13aa45e8bde2587d98bbd9 AT news DOT freeserve DOT net> <39405324 DOT 420716556 AT news DOT globalserve DOT net> <a9q0ksorcmfnk96h3du1fotrpc17oa3ou7 AT 4ax DOT com> <394095cc DOT 436991456 AT news DOT globalserve DOT net> <1352ks8jjl1mlooepatkq2pgr0mjibfmbm AT 4ax DOT com>
X-Newsreader: Forte Free Agent 1.11/32.235
Lines: 58
Date: Fri, 09 Jun 2000 17:49:39 GMT
NNTP-Posting-Host: 207.176.153.157
X-Complaints-To: news AT primus DOT ca
X-Trace: news1.tor.primus.ca 960572922 207.176.153.157 (Fri, 09 Jun 2000 13:48:42 EDT)
NNTP-Posting-Date: Fri, 09 Jun 2000 13:48:42 EDT
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

On Fri, 09 Jun 2000 16:03:10 GMT, Damian Yerrick
<Bullcr_pd_yerrick AT hotmail DOT comRemoveBullcr_p> ate too many
hallucinogenic mushrooms and wrote:

>On Fri, 09 Jun 2000 07:37:11 GMT, zargon AT hotmail DOT vom (Zargon) wrote:
>
>>[Allegro 3.9.32 doesn't work]
>>Specifically, the instructions on DJGPP have not changed much: instead
>>of just using "make" you are supposed to do "make" and then "make
>>install".
>
>This is to make it more consistent with standard practice on other
>platforms (e.g. eunuchs).

I wasn't complaining about this, indeed consistency is a worthwhile
goal in these situations since it will make the Unix ports'
installation more familiar to Unix types, and the ports consistent
among themselves, so that someone who has used Allegro 3.9.x on one
platform will find its use familiar on another.

>>Compiling Allegro for djgpp, optimised. Please wait...
>>gcc -DALLEGRO_SRC -Wall -Wno-unused -mpentium -O6 -ffast-math
>>-fomit-frame-pointer -I. -I./include -o obj/djgpp/alleg/allegro.o -c
>>src/allegro.c
>>In file included from src/allegro.c:22:
>>include/allegro/aintern.h:32: parse error before `_allegro_count'
>>include/allegro/aintern.h:32: warning: type defaults to `int' in
>>declaration of `AL_VAR'
>>include/allegro/aintern.h:32: warning: data definition has no type or
>>storage class
>>include/allegro/aintern.h:36: parse error before `_scratch_mem'
>>...
>
>Sounds like a compiler problem.  It WORKS4ME.

Surely not. The egcs I'm using is reasonably stable. It certainly
shouldn't be bombing on simple C sources!

>>C:\DJGPP\allegro>gcc --version
>>egcs-291.60
>
>Try upgrading to GCC 2.95.2 and DJGPP 2.03.

That sounds suspiciously like a downgrade to me! I'd like to keep my
Pentium optimizations, namespaces, stable exception support, and
working template support, thank you very much; especially the Pentium
optimizations, which will greatly benefit this project (the C++
features listed aren't being used in it, but I may well use them in
the future...)

>This may have been your problem.  Try unpacking Allegro somewhere else
>on your drive.

Can't have been. There's been a huge discussion on this elsewhere in
this thread. Refer to it.
-- 
Any sufficiently advanced magic is indistinguishable from
an Allegro-using C++ program compiled with gcc.