On Thursday 02 October 2008 03:18:07 Hin-Tak Leung wrote:
> But I found a rather curious issue: gcc 4.2.1-2 itself needs
> -D__USE_MINGW_ANSI_STDIO=0 to cross-build (and possibly
> native-build also?). This is surprising, because I would have
> expected it is either irrelevant (=1 and =0 should both work), or
> gcc prefers standard-compliant (=1).
> I guess gcc 4.2.1-2 predates the ANSI_STDIO change, so it just
> means it prefers the older mingw-runtime behavior, but nonetheless,
> this is surprising. Anybody wants to comment on this?
Yes, see below...
> The actual error is this (neither specified - failing during
> libgfortran): -------------
> In file included from
>tdio.h: In function 'fprintf':
>tdio.h:245: error: conflicting types for '__p___argv'
>tdlib.h:78: error: previous declaration of '__p___argv' was here
This is MinGW-bug 2117379, already reported, and already fixed in CVS;
(it comes to light when stdlib.h is #included before stdio.h, but not
if stdio.h is #included before stdlib.h). Released source will be
available with the upcoming mingwrt-3.15.1 bug fix release.