Message-ID:	<001e01c22197$3046f490$5901a8c0@firma>
From:	"Filip Sielimowicz" <filip AT hands DOT com DOT pl>
To:	<djgpp AT delorie DOT com>
References:	<010601c22109$e1375f80$7540b10a AT eu DOT broadcom DOT com>
Subject:	Re: Possible bug: djdev203 + gcc 3.1, stdarg.h: va_list definition conflicts with stdio.h
Date:	Tue, 2 Jul 2002 09:07:54 +0200
Organization:	filip AT hands DOT com DOT pl
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4133.2400
Reply-To:	djgpp AT delorie DOT com

As far as I remember, there's some info about this bug in gcc 3.x
documentation.
See DJDIR/gnu/gcc-3.x/readme.DJGPP (or something like that, I cant check it
now).

I installed gcc 3.1 yesterday and found information about some patch in this
document
(but I haven't "patched" yet ;) )

Filip Sielimowicz
http://panda.bg.univ.gda.pl/~sielim


> When I compile the following two-liner (using gcc -c)
> with DJDEV203 and GCC31B installed:
>
>     #include <stdio.h>
>     #include <stdarg.h>
>
> I get an error message about 'va_list' being redefined.
>
> It is getting stdio.h from %DJDIR%/include and stdarg.h
> from the compiler-specific include directory (which has
> no stdio.h).
>
> I notice that in my Linux copy of GCC 3.1, the compiler
> comes with its own copy of stdio.h as well, which perhaps
> avoids this conflict.
>
> Please reply personally, I don't subscribe to this list.
> Please be gentle if I've missed something obvious.
>
> Thanks,
> --
> David Monksfield
>

- Raw text -