msvcrt: scanf fix a typo

Alexandre Julliard julliard at
Sat Sep 20 05:17:10 CDT 2008

Michael Karcher <wine at> writes:

> On the other hand, for the implementation side (msvcrtd and crtdll),
> option c seems attractive to me, because it just disables the stuff we
> need disabled but allows gcc to take full advantage about knowing the C
> standard on functions where msvcrt is not incompatible. A problem with
> option C is, that it is playing a cat-and-mouse game with the gcc
> developers: As soon as they add some more checks to calling standard
> library functions that are incompatible with Microsofts extensions, we
> start to get warnings again.

The real problem is that the -fno-builtin-xxx option is broken on some
gcc versions. We used to use it, but we had to switch to a global
-fno-builtin because of this bug.

Alexandre Julliard
julliard at

More information about the wine-devel mailing list