On 27 October 2012 21:32, Igor Mitsyanko <i.mitsya...@gmail.com> wrote: > I encountered strange behavior of latest mingw gcc, it ignores unrecognized > -Wno-wombat options only in case if no other warnings are issued (configure > gccflags test doesn't issue any), otherwise I get this: > > cc1.exe: warning: unrecognized command line option > "-Wno-initializer-overrides" [enabled by default] > > This is probably a bug in mingw GCC (or perhaps I'm using it wrong), but > anyway, this makes QEMU mingw build output very noisy.
It should only warn about that in the case where it's also emitting some other warning message (in which case the idea is to say "and hey maybe this unrecognised no-wombat warning was supposed to suppress this?"), so the build isn't noisy unless it was noisy anyway because of other compile warnings. If we want to actually only pass -Wno-wombat when the gcc knows about it the right approach is to test whether gcc accepts -Wwombat. This is a two-liner patch to configure if we want to do it -- will send a patch in a moment. -- PMM
