diff options
| author | Paul Eggert <eggert@cs.ucla.edu> | 2015-01-04 01:10:26 -0800 |
|---|---|---|
| committer | Paul Eggert <eggert@cs.ucla.edu> | 2015-01-04 01:11:08 -0800 |
| commit | cde73794f61fec2a5a8676c2e36ec6634e72cdc5 (patch) | |
| tree | ee8896032f784d4cef830ee79d4b124f9dbec3dc | |
| parent | 1ac42bca8886267dac029a2f19df1a43313e0d95 (diff) | |
* INSTALL: Mention 'make WERROR_CFLAGS='.
| -rw-r--r-- | ChangeLog | 2 | ||||
| -rw-r--r-- | INSTALL | 4 |
2 files changed, 5 insertions, 1 deletions
@@ -1,5 +1,7 @@ 2015-01-04 Paul Eggert <eggert@cs.ucla.edu> + * INSTALL: Mention 'make WERROR_CFLAGS='. + Clarify 'make info' * Makefile.in (info): Use GNU make conditional rather than an '@' rule with a shell conditional, so that the builder can @@ -312,7 +312,9 @@ Use --enable-gcc-warnings to enable compile-time checks that warn about possibly-questionable C code. This is intended for developers and is useful with GNU-compatible compilers. On a recent GNU system there should be no warnings; on older and on non-GNU systems the -generated warnings may still be useful. +generated warnings may still be useful, though you may prefer building +with 'make WERROR_CFLAGS=' so that the warnings are not treated as +errors. Use --enable-silent-rules to cause 'make' to chatter less. This is helpful when combined with options like --enable-gcc-warnings that |