Date: Sun, 02 Jun 2002 19:43:28 +0300
From: "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender: halo1 AT zahav DOT net DOT il
To: "Richard Dawe" <rich AT phekda DOT freeserve DOT co DOT uk>
Message-Id: <2927-Sun02Jun2002194327+0300-eliz@is.elta.co.il>
X-Mailer: emacs 21.3.50 (via feedmail 8 I) and Blat ver 1.8.9
CC: djgpp-workers AT delorie DOT com
In-reply-to: <3CFA1583.5AC846E7@phekda.freeserve.co.uk> (message from Richard
	Dawe on Sun, 02 Jun 2002 13:54:27 +0100)
Subject: Re: DJGPP CVS & gcc 3.1 [patch included]
References: <10205280349 DOT AA23034 AT clio DOT rice DOT edu> <3CFA1583 DOT 5AC846E7 AT phekda DOT freeserve DOT co DOT uk>
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
Precedence: bulk

> Date: Sun, 02 Jun 2002 13:54:27 +0100
> From: Richard Dawe <rich AT phekda DOT freeserve DOT co DOT uk>
> 
> bash-2.04$ make all
> gcc -g mkdoc.cc -lstdcxx -o ../../hostbin/mkdoc.exe
> 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'
> make.exe: *** [../../hostbin/mkdoc.exe] Error 1
> bash-2.04$ gcc -g mkdoc.cc -lstdcxx -o ../../hostbin/mkdoc.exe
> 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'
> bash-2.04$ gcc -g -Wno-error mkdoc.cc -lstdcxx -o ../../hostbin/mkdoc.exe
> 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.