From 1c760b1c009b1f474b64bacc2b5e705e237ea198 Mon Sep 17 00:00:00 2001 From: Stefano Lattarini Date: Fri, 24 Dec 2010 18:52:05 +0100 Subject: [PATCH] Update NEWS about the warnings-over-strictness precedence. * NEWS: Automake explicit warning levels always take precedence over the implicit warning levels implied by Automake strictness. --- ChangeLog | 4 ++++ NEWS | 9 +++++++++ 2 files changed, 13 insertions(+) diff --git a/ChangeLog b/ChangeLog index 050ec97..b5eb298 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,5 +1,9 @@ 2011-01-15 Stefano Lattarini + Update NEWS about the warnings-over-strictness precedence. + * NEWS: Automake explicit warning levels always take precedence + over the implicit warning levels implied by Automake strictness. + For PR automake/547: Warnings win over strictness in AUTOMAKE_OPTIONS. Ensure that, for what concerns the options specified in diff --git a/NEWS b/NEWS index 417cc5c..bbc177d 100644 --- a/NEWS +++ b/NEWS @@ -108,6 +108,15 @@ Bugs fixed in 1.11a: - Automake now complains if a `*YFLAGS' variable has any conditional content, not only a conditional definition. + + - Explicit enabling and/or disabling of Automake warning categories + through the `-W...' options now always takes precedence over the + implicit warning level implied by Automake strictness (foreign, gnu + or gnits), regardless of the order in which such strictness and + warning flags appear. For example, a setting like: + AUTOMAKE_OPTIONS = -Wall --foreign + will cause the warnings in category `portability' to be enabled, even + if those warnings are by default disabled in `foreign' strictness. New in 1.11: -- 2.7.4