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: <39412ad4.31251750@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> <3940A2B7 DOT 57226F0C AT home DOT com> <3940a2f3 DOT 440359385 AT news DOT globalserve DOT net> <3940FA83 DOT B43AC647 AT home DOT com>
X-Newsreader: Forte Free Agent 1.11/32.235
Lines: 26
Date: Fri, 09 Jun 2000 17:40:20 GMT
NNTP-Posting-Host: 207.176.153.157
X-Complaints-To: news AT primus DOT ca
X-Trace: news1.tor.primus.ca 960572363 207.176.153.157 (Fri, 09 Jun 2000 13:39:23 EDT)
NNTP-Posting-Date: Fri, 09 Jun 2000 13:39:23 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 14:08:30 GMT, Robin Johnson <robbat2 AT home DOT com> ate
too many hallucinogenic mushrooms and wrote:

>No, i said to use the 'veryclean' target in case you had old .o files still
>around.

1. This would require me to make the dependencies, which would require
   me to use sed, which would mean booting into Linux to do it, which
   would mean setting up the gcc over there to cross-compile to DOS.
   Ouch. No thank you. Allegro should work out of the box, without
   faffing around, regardless of whether you have previously used an
   older version.
2. Old .o files can't affect anything anyways -- make will see a .o
   file with a months-old modification time and a source file just
   created/modified yesterday and say "Hmm, I think this one needs to
   be updated".
3. The errors I'm seeing also prove it isn't old .o files. An old .o
   file could only cause problems at *link* time. The errors I saw
   were *compile* time and included *parse errors* for God's sake.
   I don't see how a parse error can be caused by any "gotcha"s, only
   by an actual typo in the sources that were distributed in the zip!
   I guess it was tested on various targets but not DJGPP, and the
   error is in a conditionally-compiled section...
-- 
Any sufficiently advanced magic is indistinguishable from
an Allegro-using C++ program compiled with gcc.