Mail Archives: djgpp/2000/06/09/07:14:05
On Fri, 09 Jun 2000 07:53:58 GMT, Robin Johnson <robbat2 AT home DOT com> ate
too many hallucinogenic mushrooms and wrote:
>> I am astonished that a severe showstopper at compile time on Allegro's
>> *original platform* would make it into a released zip file. Of course,
>> in unpacking the thing I probably overwrote the previous, known-good
>> Allegro 3.12...
>
>There is the problem...
>do 'make veryclean' before you try 'make' again!
That's incorrect. The documentation says that the "clean" and
"veryclean" targets are used *after* installation, to free up disk
space by removing .o files and the like. It also says that after a
"make veryclean" if you want to build the library again at a later
date you have to make the dependencies again, and for that you have to
have sed; I don't have sed so this is simply not an option.
The existence of files from previous versions cannot possinly have any
effect anyways. Any source file referenced in the makefile, or
included into another source file, will have been included in the zip,
and I took care that any old files were overwritten. Therefore, no
files from 3.12 can possibly be being seen by make or by the compiler.
Unless of course someone was silly enough to mention in the makefile
or in a #include a file not in the zip, but which existed in 3.12; in
that case it will be seeing a 3.12 file, but cleaning everything out
would then simply cause me to get a file not found error of some sort
instead.
--
Any sufficiently advanced magic is indistinguishable from
an Allegro-using C++ program compiled with gcc.
- Raw text -