From cf0bb5e05d89d9239a819b696a85532a582c8d38 Mon Sep 17 00:00:00 2001
From: =?utf8?q?P=C3=A1draig=20Brady?= <P@draigBrady.com>
Date: Wed, 11 Mar 2009 12:09:08 +0000
Subject: [PATCH] maint: Document how to best to enable gcc warnings for
 developers

* README-hacking: Mention --enable-gcc-warnings configure option
* configure.ac: Don't scare developers away from using gcc warnings
---
 README-hacking | 2 +-
 configure.ac   | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/README-hacking b/README-hacking
index 433ef4102f..668d8d9117 100644
--- a/README-hacking
+++ b/README-hacking
@@ -53,7 +53,7 @@ which are extracted from other source packages:
 
 And there you are!  Just
 
-        $ ./configure
+        $ ./configure #[--enable-gcc-warnings]
         $ make
         $ make check
 
diff --git a/configure.ac b/configure.ac
index f10191fa8d..f3172ad985 100644
--- a/configure.ac
+++ b/configure.ac
@@ -46,7 +46,7 @@ coreutils_MACROS
 
 AC_ARG_ENABLE([gcc-warnings],
   [AS_HELP_STRING([--enable-gcc-warnings],
-		  [turn on lots of GCC warnings (not recommended)])],
+		  [turn on lots of GCC warnings (for developers)])],
   [case $enableval in
      yes|no) ;;
      *)      AC_MSG_ERROR([bad value $enableval for gcc-warnings option]) ;;
-- 
2.47.3