GCC headers and DJGPP port

[Mark E.]

> Mike Stump wrote:
> > A sure sign of a non-maintained port, is a system with its own
> > vararg.h...
> 
> Or is it a sign of system which had its own little GCC fork previously?

Which we're actively trying to eliminate now. But when patches to close this 
gap go undealt with while others are quickly handled, it is tempting to think 
the maintainers aren't inclined to help eliminate the gap. 

Mark