m4: fix setting of warning flags

When adding the -std=gnu99 flag, we set $wantwarn instead
of appending to it. This meant all the compiler warnings
were accidentally discarded.

Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>

diff --git a/m4/virt-compile-warnings.m4 b/m4/virt-compile-warnings.m4
index 411d2574659d20bab53ada124458896c669a36a5..26f231f97e8e37b030981749ad1946105412adb5 100644 (file)
--- a/m4/virt-compile-warnings.m4
+++ b/m4/virt-compile-warnings.m4
@@ -192,7 +192,7 @@ AC_DEFUN([LIBVIRT_COMPILE_WARNINGS],[
     # Request the gnu99 standard which is the best choice with
     # gcc 4.8.0. Not a warning flag, but the probing mechanism
     # is convenient
-    wantwarn="-std=gnu99"
+    wantwarn="$wantwarn -std=gnu99"
 
     # Check for $CC support of each warning
     for w in $wantwarn; do