+2001-11-22 Akim Demaille <akim@epita.fr>
+
+ * doc/autoconf.texi (Installation Directory Variables): Englishoes
+ spotted by Jim Meyering.
+
2001-11-16 Paul Eggert <eggert@twinsun.com>
-
+
This patch implements a `long double' suggestion by Oliver Kiddle.
-
+
* lib/autoconf/c.m4 (AC_LANG_BOOL_COMPILE_TRY(C)): Make the array
static, to catch errors if the value isn't known at compile-time
and the compiler supports dynamic arrays. Change its name from
better than double. Catch a bug in GCC 2.95.2 x86.
* doc/autoconf.texi (C Compiler): Document the above.
* NEWS: Likewise.
-
+
2001-11-13 Akim Demaille <akim@epita.fr>
* tests/m4sh.at (LINENO): Protect from autom4te's substitution by
Most of these variables have values that rely on @code{prefix} or
-@code{exec_prefix}. It is on purpose that the directory output
+@code{exec_prefix}. It is deliberate that the directory output
variables keep them unexpanded: typically @samp{@@datadir@@} will be
replaced by @samp{$@{prefix@}/share}, not @samp{/usr/local/share}.
@item make
she can still specify a different prefix from the one specified to
@command{configure}, in which case, if needed, the package shall hard
-code dependencies to her late desires.
+code dependencies corresponding to the make-specified prefix.
@item make install
she can specify a different installation location, in which case the
remains being defined as @samp{$@{prefix@}/share} to depend upon the
current value of @code{prefix}.
-A corollary is that you should not use these variables but in Makefiles.
-For instance, instead of trying to evaluate @code{datadir} in
-@file{configure} and hardcoding it in Makefiles using
+A corollary is that you should not use these variables except in
+Makefiles. For instance, instead of trying to evaluate @code{datadir}
+in @file{configure} and hardcoding it in Makefiles using
e.g. @samp{AC_DEFINE_UNQUOTED(DATADIR, "$datadir")}, you should add
@samp{-DDATADIR="$(datadir)"} to your @code{CPPFLAGS}.