+2009-10-09 Bruno Haible <bruno@clisp.org>
+ Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
+
+ Recommend `sh -n' debugging, and public result variables for macros.
+ * doc/autoconf.texi (Debugging): Recommend to use "bash -n
+ configure". Recommend the use of result variables as an
+ alternative to run-if-true/run-if-false parameters.
+
2009-10-05 Bruno Haible <bruno@clisp.org>
* doc/autoconf.texi (Particular Functions): Swap sections about
or listing some macro names and watch @command{m4} expand its input
verbosely (@pxref{Debugging via autom4te}).
+@item
+Sometimes @command{autoconf} succeeds but the generated
+@command{configure} script has invalid shell syntax. You can detect this
+case by running @samp{bash -n configure} or @samp{sh -n configure}.
+If this command fails, the same tips apply, as if @command{autoconf} had
+failed.
+
@item
Debugging @command{configure} script execution may be done by sprinkling
pairs of @code{set -x} and @code{set +x} into the shell script before
@item
by not requiring users of your macro to use the cache variables.
Instead, expose the result of the test via @var{run-if-true} and
-@var{run-if-false} parameters.
+@var{run-if-false} parameters. If the result is not a boolean,
+then provide it through documented shell variables.
@end itemize