>From fddbb05c9c8722cfb1b8b3d8356d43ff9ca4e4bf Mon Sep 17 00:00:00 2001 From: Pavel Raiskup Date: Fri, 8 Feb 2013 13:42:38 +0100 Subject: [PATCH 3/3] docs: Mention consequences with AC_CONFIG_MACRO_DIRS * doc/automake.texi: Document possible problems if user wants to specify AC_CONFIG_MACRO_DIRS to point somewhere else then to the directory 'm4'. See: --- doc/automake.texi | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/doc/automake.texi b/doc/automake.texi index e700ab9..944fd9d 100644 --- a/doc/automake.texi +++ b/doc/automake.texi @@ -3614,6 +3614,23 @@ AC_CONFIG_MACRO_DIRS([m4]) @command{aclocal} will then take care of automatically adding @file{m4/} to its search path for m4 files. +There is strictly encouraged not to change the 'm4' directory name to +some different name at the moment. There still exist several +incompatibilities among tools which may be run during @code{autoreconf} and +how they deal with its custom macros. Note that (e.g.) address@hidden installs its macros into first @code{-I DIR} directory +set by @code{ACLOCAL_AMFLAGS} macro (which is not supported now), otherwise +defaults to store it into @file{m4} dir. You also need to specify address@hidden in @code{AC_CONFIG_MACRO_DIRS} at the first place if the address@hidden directory does not exist in distribution by default (to be +created by @code{aclocal} or other tool). The least problematic way seems +to be now: + address@hidden +configure.ac: AC_CONFIG_MACRO_DIRS([m4]) +Makefile.am: # **NO** ACLOCAL_AMFLAGS address@hidden example + When @samp{aclocal} is run, it will build an @file{aclocal.m4} that @code{m4_include}s any file from @file{m4/} that defines a required macro. Macros not found locally will still be searched in -- 1.7.11.7