summaryrefslogtreecommitdiff
path: root/README-hacking
diff options
context:
space:
mode:
authorPádraig Brady <P@draigBrady.com>2009-03-11 12:09:08 +0000
committerPádraig Brady <P@draigBrady.com>2009-03-11 14:52:52 +0000
commitcf0bb5e05d89d9239a819b696a85532a582c8d38 (patch)
tree6a3bd49b1adcb3f188968bc598450eba592a8781 /README-hacking
parent20dc2a6a61e990b199c468c6972f7f560a4dbe0b (diff)
downloadcoreutils-cf0bb5e05d89d9239a819b696a85532a582c8d38.tar.xz
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
Diffstat (limited to 'README-hacking')
-rw-r--r--README-hacking2
1 files changed, 1 insertions, 1 deletions
diff --git a/README-hacking b/README-hacking
index 433ef4102..668d8d911 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