From:	sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id:	<10206021956.AA17408@clio.rice.edu>
Subject:	Re: DJGPP CVS & gcc 3.1 [patch included]
To:	djgpp-workers AT delorie DOT com, eliz AT is DOT elta DOT co DOT il (Eli Zaretskii)
Date:	Sun, 2 Jun 2002 14:56:50 -0500 (CDT)
Cc:	rich AT phekda DOT freeserve DOT co DOT uk (Richard Dawe)
In-Reply-To:	<2927-Sun02Jun2002194327+0300-eliz@is.elta.co.il> from "Eli Zaretskii" at Jun 02, 2002 07:43:28 PM
X-Mailer:	ELM [version 2.5 PL2]
Mime-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

> > In file included from mkdoc.cc:14:
> > c:/djgpp/lib/gcc-lib/djgpp/3.1/include/stdarg.h:110: conflicting types for `
> >    typedef char*va_list'
> > c:/djgpp/include/stdio.h:35: previous declaration as `typedef void*va_list'
> > 
> > So I think the only way is to copy sys/djtypes.h from CVS to the DJGPP
> > installation.
> 
> No, I think we should rather do something inside mkdoc.cc to avoid the
> error.  For example, we could copy the relevant parts of stdio.h into
> mkdoc.cc instead if including stdio.h.  Ugly, but effective and robust.

I'm already planning to provide an updated djtypes.h to fix this in the
refresh++.  mkdoc.cc does nothing special, it just includes stdio.h and
stdarg.h.  This is a case that GCC 3.1 just won't work at all with the
current 2.03 headers, and they must be replaced.  Yes, it's a real PITA.

- Raw text -