From 07cbb610ba6c116af6c81c2b53fa74f4fe1e5aba Mon Sep 17 00:00:00 2001
From: Doug Goldstein <cardoe@cardoe.com>
Date: Mon, 24 Sep 2012 18:44:34 -0500
Subject: [PATCH] Update how to compile with -Werror

--enable-compile-warnings=error has been renamed to --enable-werror so
update the HACKING and the hacking.html to reflect that.
---
 HACKING              | 5 +++--
 docs/hacking.html.in | 6 ++++--
 2 files changed, 7 insertions(+), 4 deletions(-)

diff --git a/HACKING b/HACKING
index da5e771bd3..d765be9339 100644
--- a/HACKING
+++ b/HACKING
@@ -73,9 +73,10 @@ things).
 and don't care much about released versions.
 
 (5) Run the automated tests on your code before submitting any changes. In
-particular, configure with compile warnings set to -Werror:
+particular, configure with compile warnings set to -Werror. This is done
+automatically for a git checkout; from a tarball, use:
 
-  ./configure --enable-compile-warnings=error
+  ./configure --enable-werror
 
 and run the tests:
 
diff --git a/docs/hacking.html.in b/docs/hacking.html.in
index a97dc225f4..9de5eb1962 100644
--- a/docs/hacking.html.in
+++ b/docs/hacking.html.in
@@ -74,9 +74,11 @@
       <li>Make sure your patches apply against libvirt GIT.  Developers
         only follow GIT and don't care much about released versions.</li>
       <li><p>Run the automated tests on your code before submitting any changes.
-          In particular, configure with compile warnings set to -Werror:</p>
+          In particular, configure with compile warnings set to
+          -Werror.  This is done automatically for a git checkout; from a
+          tarball, use:</p>
 <pre>
-  ./configure --enable-compile-warnings=error
+  ./configure --enable-werror
 </pre>
         <p>
           and run the tests: