>From 611310ec5029aa2b5de74a70733b3cd7106034b9 Mon Sep 17 00:00:00 2001 From: Paul Eggert Date: Sun, 4 Jan 2015 01:10:26 -0800 Subject: [PATCH] * INSTALL: Mention 'make WERROR_CFLAGS='. --- ChangeLog | 2 ++ INSTALL | 4 +++- 2 files changed, 5 insertions(+), 1 deletion(-) diff --git a/ChangeLog b/ChangeLog index 8051263..36edfe6 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,5 +1,7 @@ 2015-01-04 Paul Eggert + * 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 diff --git a/INSTALL b/INSTALL index 6850c7d..1ed2698 100644 --- a/INSTALL +++ b/INSTALL @@ -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 -- 2.1.0