From 203d0775e6a9c0e04d896d24b45eec614d92c230 Mon Sep 17 00:00:00 2001 From: Stefano Lattarini Date: Tue, 24 Dec 2013 22:02:15 +0100 Subject: TAP driver: no need to invoke AC_PROG_AWK directly It is already required by AM_INIT_AUTOMAKE anyway. * doc/automake.texi: Adjust examples. * t/tap-doc2.sh: Adjust documentation-tracking test. * m4/init.m4 (AM_INIT_AUTOMAKE): Explicitly tell that the AC_PROG_AWK requirement is also needed whenever the TAP driver is used. Signed-off-by: Stefano Lattarini --- doc/automake.texi | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) (limited to 'doc') diff --git a/doc/automake.texi b/doc/automake.texi index cd33ad7c3..645e7298f 100644 --- a/doc/automake.texi +++ b/doc/automake.texi @@ -9650,10 +9650,9 @@ Currently, the TAP driver that comes with Automake requires some by-hand steps on the developer's part (this situation should hopefully be improved in future Automake versions). You'll have to grab the @file{tap-driver.sh} script from the Automake distribution by hand, copy it in your source tree, -add a call to @code{AC_PROG_AWK} in @file{configure.ac} to search for a -proper awk program, and use the Automake support for third-party test -drivers to instruct the harness to use the @file{tap-driver.sh} script -and that awk program to run your TAP-producing tests. See the example +and use the Automake support for third-party test drivers to instruct the +harness to use the @file{tap-driver.sh} script and the awk program found +by @code{AM_INIT_AUTOMAKE} to run your TAP-producing tests. See the example below for clarification. Apart from the options common to all the Automake test drivers @@ -9709,7 +9708,6 @@ AC_CONFIG_AUX_DIR([build-aux]) AM_INIT_AUTOMAKE([foreign -Wall -Werror]) AC_CONFIG_FILES([Makefile]) AC_REQUIRE_AUX_FILE([tap-driver.sh]) -AC_PROG_AWK AC_OUTPUT % @kbd{cat Makefile.am} -- cgit v1.2.1