+2010-04-22 Joel James Adamson <joel@chondestes.bio.unc.edu> (tiny change)
+
+ Add a paragraph to FAQ on Debugging configure scripts.
+ * doc/autoconf.texi (Debugging): Mention inspecting config.log.
+ * THANKS: Update.
+
2010-04-05 Eric Blake <eblake@redhat.com>
Fix m4_cr_all for EBCDIC.
Jiro Takabatake jiro@din.or.jp
Jochen Friedrich jochen@scram.de
Joel E. Denny jdenny@ces.clemson.edu
+Joel James Adamson joel@chondestes.bio.unc.edu
Joey Mingrone joey@mingrone.org
Johan Danielsson joda@pdc.kth.se
John Calcote john.calcote@gmail.com
@ref{Cache Variable Names}; the precise semantics of undocumented
variables are often internal details, subject to change.
@end itemize
+
+@item
+Alternatively, @command{configure} may produce invalid results because
+of uncaught programming errors, in your package or in an upstream
+library package. For example, when @code{AC_CHECK_LIB} fails to find a
+library with a specified function, always check @file{config.log}. This
+will reveal the exact error that produced the failing result: the
+library linked by @code{AC_CHECK_LIB} probably has a fatal bug.
@end itemize
Conversely, as macro author, you can make it easier for users of your