Ralf Wildenhues <[EMAIL PROTECTED]> writes:
> This is neither documented nor is it a desirable situation:
> http://lists.gnu.org/archive/html/autoconf-patches/2006-05/msg00052.html
> but it ended up being part of Autoconf for simplicity of the code (or
> maybe just by chance?):
> http://lists.gnu.org/archive/html/autoconf-patches/2006-05/msg00142.html
Just by chance; I didn't think about it.
> * doc/autoconf.texi (Particular Programs): Mention that
> @INSTALL@ and @MKDIR_P@ may vary for different output files.
> Reported by Alexandre Duret-Lutz.
Thanks. I installed that, with the following slightly-terser wording:
--- doc/autoconf.texi 22 Aug 2006 19:51:18 -0000 1.1070
+++ doc/autoconf.texi 24 Aug 2006 16:58:34 -0000
@@ -3652,6 +3652,9 @@ default directories) to determine @var{d
the variables @code{INSTALL_PROGRAM} and @code{INSTALL_SCRIPT} to
@[EMAIL PROTECTED]@}} and @code{INSTALL_DATA} to @[EMAIL PROTECTED]@} -m 644}.
[EMAIL PROTECTED]@@INSTALL@@} is special, as its value may vary for different
+configuration files.
+
This macro screens out various instances of @command{install} known not to
work. It prefers to find a C program rather than a shell script, for
speed. Instead of @file{install-sh}, it can also use @file{install.sh},
@@ -3703,6 +3706,9 @@ directory, and conversely a makefile sho
$(FOO)} if @var{FOO} might yield a value that begins with @samp{-}.
Finally, @code{AS_MKDIR_P} does not check for race condition
vulnerability, whereas @code{AC_PROG_MKDIR_P} does.
+
[EMAIL PROTECTED]@@MKDIR_P@@} is special, as its value may vary for different
+configuration files.
@end defmac
@defmac AC_PROG_LEX
