summaryrefslogtreecommitdiff
path: root/README-hacking
diff options
context:
space:
mode:
authorJim Meyering <meyering@redhat.com>2009-10-28 08:49:51 +0100
committerJim Meyering <meyering@redhat.com>2009-10-28 18:13:44 +0100
commit536a1fbe5ff47078d515a41ea4b45c4e0d794da2 (patch)
tree8227fba70ede6536db8890e493534093439c32b5 /README-hacking
parentce22916610d24bf29675a6761df957371b0b2376 (diff)
downloadcoreutils-536a1fbe5ff47078d515a41ea4b45c4e0d794da2.tar.xz
doc: tell --enable-gcc-warnings users where to report problems
* README-hacking: Add a caveat for --enable-gcc-warnings.
Diffstat (limited to 'README-hacking')
-rw-r--r--README-hacking8
1 files changed, 7 insertions, 1 deletions
diff --git a/README-hacking b/README-hacking
index c5d31284e..014114d87 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.