On 2017-10-08 19:26, Mark Thompson wrote: > The test in configure passes, I think because: > > <https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html>: > """ > When an unrecognized warning option is requested (e.g., -Wunknown-warning), > GCC emits a diagnostic stating that the option is not recognized. However, if > the -Wno- form is used, the behavior is slightly different: no diagnostic is > produced for -Wno-unknown-warning unless other diagnostics are being > produced. This allows the use of new -Wno- options with old compilers, but if > something goes wrong, the compiler warns that an unrecognized option is > present. > """ > > Not sure exactly how to fix that. Could we replace the check with something > like "-Werror=bool-operation", which does error out when it doesn't find the > warning option, and only add the "-Wno-bool-operation" if that works?
It seems that this would be the way to fix this function. I like this idea. -- regards Helmut K. C. Tessarek KeyID 0xF7832007C11F128D Key fingerprint = 28A3 1666 4FE8 D72C CFD5 8B23 F783 2007 C11F 128D /* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */ _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
