From: Jim Meyering <meyering@redhat.com>
Date: Wed, 28 Oct 2009 07:49:51 +0000 (+0100)
Subject: doc: tell --enable-gcc-warnings users where to report problems
X-Git-Tag: v8.1~61
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=536a1fbe5ff47078d515a41ea4b45c4e0d794da2;p=thirdparty%2Fcoreutils.git

doc: tell --enable-gcc-warnings users where to report problems

* README-hacking: Add a caveat for --enable-gcc-warnings.
---

diff --git a/README-hacking b/README-hacking
index c5d31284e5..014114d878 100644
--- a/README-hacking
+++ b/README-hacking
@@ -35,7 +35,7 @@ which are extracted from other source packages:
 
 And there you are!  Just
 
-        $ ./configure --quiet #[--enable-gcc-warnings]
+        $ ./configure --quiet #[--enable-gcc-warnings] [*]
         $ make
         $ make check
 
@@ -48,6 +48,12 @@ should output no difference.
 
 Enjoy!
 
+[*] The --enable-gcc-warnings option is useful only with glibc
+and with a very recent version of gcc.  You'll probably also have
+to use recent system headers.  If you configure with this option,
+and spot a problem, please be sure to send the report to the bug
+reporting address of this package, and not to that of gnulib, even
+if the problem seems to originate in a gnulib-provided file.
 -----
 
 Copyright (C) 2002-2009 Free Software Foundation, Inc.