From deb0c2566b3ef5e7a28072f94a6ddacdc02377ab Mon Sep 17 00:00:00 2001 From: Vadim Zeitlin Date: Thu, 20 Sep 2018 17:40:11 +0200 Subject: [PATCH] Document the change to unknown options handling in configure They used to be silently ignored, but are flagged as errors since aa7e10bb0919982bfdc510bd9cdc8b84d621d80b --- docs/changes.txt | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docs/changes.txt b/docs/changes.txt index e1af792208..a57f7068a1 100644 --- a/docs/changes.txt +++ b/docs/changes.txt @@ -86,6 +86,13 @@ Changes in behaviour which may result in build errors not long. Its return value hasn't changed, however, and is still always either true or false, so normally the existing code should continue to work. +- configure only accepts the options it knows about now and doesn't silently + ignore all the rest. If you get errors about unknown options, you may either + specify --disable-option-checking argument to continue accepting them (which + only ever makes sense if you pass these options to sub-configure scripts) or, + e.g. if the error is due to spelling an option name wrongly, fixing or + removing its name. + 3.1.2: (released 2018-??-??) ----------------------------