autoconf

mirror of git://git.sv.gnu.org/autoconf synced 2024-11-27 01:49:56 +08:00

History

Pavel Roskin ae60935d08 * tests/tools.at (autoupdating AC_LINK_FILES): Invoke autoconf like in the rest of the tests.		2000-11-01 15:20:46 +00:00
..
.cvsignore	More stuff to ignore: config.h config.hin experr expout state*	2000-10-30 16:47:42 +00:00
aclocal.m4
atconfig.in
atgeneral.m4	* tests/atgeneral.m4 (AT_CHECK): Warn if the expected exit status	2000-10-30 03:24:44 +00:00
atspecific.m4
base.at	Use AC_MSG_ERROR in the test suite, not just `exit'.	2000-10-27 14:15:28 +00:00
m4sh.at	Use AC_MSG_ERROR in the test suite, not just `exit'.	2000-10-27 14:15:28 +00:00
m4sugar.at
Makefile.am	Use AC_MSG_ERROR in the test suite, not just `exit'.	2000-10-27 14:15:28 +00:00
Makefile.in	Use AC_MSG_ERROR in the test suite, not just `exit'.	2000-10-27 14:15:28 +00:00
mktests.sh
README	Use AC_MSG_ERROR in the test suite, not just `exit'.	2000-10-27 14:15:28 +00:00
semantics.at	Use AC_MSG_ERROR in the test suite, not just `exit'.	2000-10-27 14:15:28 +00:00
suite.at	* tests/suite.at: Move "-- Autoconf --" to the second line.	2000-10-27 14:43:44 +00:00
syntax.at
tools.at	* tests/tools.at (autoupdating AC_LINK_FILES): Invoke autoconf	2000-11-01 15:20:46 +00:00
torture.at
update.at

README

							-*- outline -*-

This directory holds the M4sugar, M4sh and Autoconf test suites.

Here are a few rules on how to write tests.

* Autoconf

** Use of `exit'
Don't directly `exit 1' or `exit 77', rather use `AC_MSG_ERROR'.
First of all because when we have to read the test suite logs we are
happy to know why `configure' exited thanks to the error
message. Secondly, because `configure' traps the `exit' and pretty
many shells fail to set $? to 77 when trapping `exit 77'.  This
results in the test suite not being able to check the exit status.

** AC_MSG_ERROR
Of course, since macro names are forbidden in `configure', if you
really want to mention the macro name, you'll have to do without
including `A?_' in the output.