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 433ef4102f7d62d28ef393e668c915c75da318e3..668d8d911771559a75d524dca4b8ea8ec474f0f6 100644 (file)
--- 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 f10191fa8d05b6ad5199b1ec338fcf0791cb88f5..f3172ad985d17891a2906085a5f73563c515d526 100644 (file)
--- 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]) ;;