Mail Archives: djgpp/2000/06/09/15:02:04
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.
- Raw text -