Mail Archives: djgpp/2002/08/12/02:15:30
> rebooted and proceeded right to the Allegro compile. I got to the
> "va_list" error termination and searched here to find the discussion.
> To my amazement, the discussion is actually quite fresh!
We are in the process of releasing a refreshed djdev203.zip with the
"fixed" sys/djtypes.h to make GCC 3.1 happy. (Just not enough hours
in the day, when it's the last priority as volunteer work ...)
> I had to do a file search to find readme.DJGPP (I really couldn't find
> it by browsing even though I knew what I was now looking for.)
> What do we do with the cryptic message at the end of this hidden
> readme file??
It's a patch - ideally you would extract it and run the patch utility
(if you installed it) - if not you could carefully hand edit the changes
into djtypes.h ... Or I believe you can just get
http://clio.rice.edu/djgpp/v203u2/djdev203_u2.zip
and that will "upgrade" a December 2001 refresh to include the gcc 3.1
fixes.
> I would have thought this would have been mentioned in the
> Installation Instruction page that zippicker reveals. I can't find
> any reference to this in Eli's FAQ either. (BTW Eli is a champ!)
This problem is more recent than either the most recent FAQ or the
last update to the zip picker instructions. It's only seen with GCC 3.1,
earlier releases don't have this problem.
> I also recall that I had no success on a Win2K installation a couple
> of months ago. I see the > reference to a fixup page in readme.DJGPP at
> http://clio.rice.edu/djgpp/win2k/main.htm
I use exclusively Win2K for my DJGPP development, so if you pick up the
recent files the key pieces (built since December 2001) should work on
Win2K. If the binary is older, you may need to build an update yourself.
- Raw text -