+2003-01-22 Alexandre Duret-Lutz <adl@gnu.org>
+
+ * automake.texi (Python): Explain that directory variables start
+ with either ${prefix} or ${exec_prefix}, and point to the
+ `Installation Directory Variables' section of the Autoconf manual.
+
2003-01-21 Alexandre Duret-Lutz <adl@gnu.org>
* lib/am/distdir.am (top_distdir, distdir): Define these
@code{sys.version[:3]}.
@item PYTHON_PREFIX
-The string @code{$prefix}. This term may be used in future work
+The string @code{$@{prefix@}}. This term may be used in future work
which needs the contents of Python's @code{sys.prefix}, but general
consensus is to always use the value from configure.
@item PYTHON_EXEC_PREFIX
-The string @code{$exec_prefix}. This term may be used in future work
+The string @code{$@{exec_prefix@}}. This term may be used in future work
which needs the contents of Python's @code{sys.exec_prefix}, but general
consensus is to always use the value from configure.
@samp{$(pyexecdir)/$(PACKAGE)}.
@end vtable
+All these directory variables have values that start with either
+@code{$@{prefix@}} or @code{$@{exec_prefix@}} unexpanded. This works
+fine in @file{Makefiles}, but it makes these variables hard to use in
+@file{configure}. This is mandated by the GNU conding standard, so
+that the user can run @code{make prefix=/foo install}. The Autoconf
+manual has a section with more details on this topic
+(@pxref{Installation Directory Variables, , Installation Directory
+Variables, autoconf, The Autoconf Manual}).
+
@node Documentation, Install, Other GNU Tools, Top
@chapter Building documentation