Mail Archives: djgpp/2001/09/12/03:51:13
Matthew Smith wrote:
>
> > The MAKE seems to work OK until a file called DAT2S.EXE is built
> > and then executed this is the error message at that point:
>
> I think it is probably setup.dat which is at fault, and dat2s.exe is
> choking on that.
> setup.dat is a brand new file, while dat2s.exe has been working for
> years.
I don't have the exact error message handy (I'm at work), but I
think DAT2S was built and was in the process of executing when it
crashed. It may well have been because of the file it was processing.
> You didn't mention what version of Allegro you have, and whether it is
> a WIP (current release) or CVS (in development) version. I have not
> seen this problem mentioned by anyone else, please be patient until
> someone manages to reproduce or explain the crash.
As you've probably noticed, I _did_ get it to compile once I
realized I was using a test version of GCC. I apologize for the false
alarm. It was a silly mistake. GCC 3.0 (alpha) has been working for
me so well that I completely forgot I was using an alpha version!
I was compiling Allegro 3.9.37, the latest edition available on the
Allegro site (before I transferred my files to the new computer a
couple of months ago). I had seen _not_ to use ALLEG312.ZIP, which is
the latest available on the djgpp simtelnet site, by looking at the
DJGPP archives. I've been wanting to try it out for over a year,
since I started making a game (from scratch, no help from libraries)
with some students here at the college where I work. The students
bailed out, and I put that game on the shelf... and I'm just now
getting around to trying out Allegro.
Once again, I apologize for the false alarm. I was simply using an
unstable compiler.
Thanks,
Dave W.
- Raw text -