From: Pádraig Brady <P@draigBrady.com>
Date: Wed, 11 Mar 2009 12:09:08 +0000 (+0000)
Subject: maint: Document how to best to enable gcc warnings for developers
X-Git-Tag: v7.2~43
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=cf0bb5e05d89d9239a819b696a85532a582c8d38;p=thirdparty%2Fcoreutils.git

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
---

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]) ;;