Mail Archives: djgpp-workers/2002/06/03/02:26:52
On Sun, 2 Jun 2002, Eli Zaretskii wrote:
> > 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.
>
mkdoc.cc should be build with host environment when cross-buildinng
DJGPP libc, for example under Linux. Of course we can put something like
#ifdef __DJGPP__
... needed stuff from stdio.h
#else
#include <stdio.h>
#endif
there
Andris
- Raw text -