From: Christophe CURIS <[email protected]> When autoconf encounters a macro name that it does not know, it assumes that it is just a standard keyword that needs to end up in the generated configure script.
This patch teaches m4 about the syntax used for our macros so it can now that it is supposed to be a macro, and then it can stop and report the problem. Signed-off-by: Christophe CURIS <[email protected]> --- m4/windowmaker.m4 | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/m4/windowmaker.m4 b/m4/windowmaker.m4 index 6658314..3171cfc 100644 --- a/m4/windowmaker.m4 +++ b/m4/windowmaker.m4 @@ -16,6 +16,14 @@ # with this program; if not, write to the Free Software Foundation, Inc., # 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA. + +dnl Tell m4 to not allow stuff starting with "WM_" in the generated file +dnl because this is likely a problem of a macro that was not expanded as +dnl expected (with an exception for an already used variable name) +m4_pattern_forbid([^_?WM_]) +m4_pattern_allow([^WM_OSDEP(_[A-Z]*)?$]) + + dnl dnl WM_CHECK_XFT_VERSION(MIN_VERSION, [ACTION-IF-FOUND [,ACTION-IF-NOT-FOUND]]) dnl -- 1.8.4.rc3 -- To unsubscribe, send mail to [email protected].
