From 4d2b96655fda2324faf0722149a4b3c62599cbcb Mon Sep 17 00:00:00 2001
From: =?utf8?q?Daniel=20P=2E=20Berrang=C3=A9?= <berrange@redhat.com>
Date: Tue, 8 Oct 2019 13:41:19 +0100
Subject: [PATCH] m4: fix setting of warning flags
MIME-Version: 1.0
Content-Type: text/plain; charset=utf8
Content-Transfer-Encoding: 8bit

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>
---
 m4/virt-compile-warnings.m4 | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/m4/virt-compile-warnings.m4 b/m4/virt-compile-warnings.m4
index 411d257465..26f231f97e 100644
--- 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
-- 
2.47.2