[cairo] [PATCH 2/2] configure : fix unrecognized -Wno option

Gilles Espinasse g.esp at free.fr
Sat Oct 20 11:22:51 PDT 2012

Signed-off-by: Gilles Espinasse <g.esp at free.fr>

gcc-4.4 and later accept every -Wno option
Test for the option without no in the name to check if the option is supported.

Each time a warning is emitted and without this fix, on gcc-4.4 that will add this warning:
cc1: warning: unrecognized command line option "-Wno-unused-but-set-variable"

bugs.freedesktop.org #51633, rediffed after 1.12.4
 build/configure.ac.warnings |   11 +++++++----
 1 files changed, 7 insertions(+), 4 deletions(-)

diff --git a/build/configure.ac.warnings b/build/configure.ac.warnings
index 9b9c742..06c4781 100644
--- a/build/configure.ac.warnings
+++ b/build/configure.ac.warnings
@@ -21,8 +21,11 @@ MAYBE_WARN="-Wall -Wextra \
 -Wno-missing-field-initializers -Wno-unused-parameter \
 -Wno-attributes -Wno-long-long -Winline"
+# New -Wno options should be added here
+# gcc-4.4 and later accept every -Wno- option but may complain later that this
+# option is unknow each time another warning happen.
 # -Wunused-but-set-variable is too noisy at present
 dnl Sun Studio 12 likes to rag at us for abusing enums like
 dnl having cairo_status_t variables hold cairo_int_status_t
@@ -48,8 +51,6 @@ MAYBE_WARN="$MAYBE_WARN -fno-strict-aliasing -fno-common"
 dnl Also to turn various gcc/glibc-specific preprocessor checks
 # invalidate cached value if MAYBE_WARN has changed
 if test "x$cairo_cv_warn_maybe" != "x$MAYBE_WARN"; then
 	unset cairo_cv_warn_cflags
@@ -72,7 +73,9 @@ AC_CACHE_CHECK([for supported warning flags], cairo_cv_warn_cflags, [
 	for W in $MAYBE_WARN; do
+	for W in $NO_WARN; do
+	done

More information about the cairo mailing list