[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

TESTSUITEFLAGS example (was: [GNU Autoconf 2.59c] testsuite: 75 78 89 10

From: Ralf Wildenhues
Subject: TESTSUITEFLAGS example (was: [GNU Autoconf 2.59c] testsuite: 75 78 89 102 failed)
Date: Wed, 24 May 2006 21:58:07 +0200
User-agent: Mutt/1.5.11+cvs20060403

Hi Eric,

* Eric Blake wrote on Wed, Apr 19, 2006 at 04:40:39AM CEST:
> According to Ralf Wildenhues on 4/18/2006 11:24 AM:
> > Rerunning the test with
> >   make check TESTSUITEFLAGS='-v -d -x 75'
> That's the sort of advice I would find useful in the manual.  Right now,
> the 'Making testsuite scripts' node mentions how to hook an autotest
> testsuite into your Makefile, but does not give advice on how to document
> to the end user on how to rerun just a particular test.  I'm so used to
> automake's TESTS variable, that I did not think to try TESTSUITEFLAGS.

Definitely a good idea.

How about this?


        * doc/autoconf.texi (Making testsuite Scripts): Add an example
        how to use TESTSUITEFLAGS.  Suggested by Eric Blake.

Index: doc/autoconf.texi
RCS file: /cvsroot/autoconf/autoconf/doc/autoconf.texi,v
retrieving revision 1.1018
diff -u -r1.1018 autoconf.texi
--- doc/autoconf.texi   20 May 2006 05:39:03 -0000      1.1018
+++ doc/autoconf.texi   22 May 2006 18:50:05 -0000
@@ -17634,6 +17640,14 @@
 and manage to have @file{} and @code{$(EXTRA_DIST)}
+With all this in place, and if you have not initialized @samp{TESTSUITEFLAGS}
+within your Makefile, you can fine-tune test suite execution with this 
+for example:
+make check TESTSUITEFLAGS='-v -d -x 75 -k AC_PROG_CC CFLAGS=-g'
address@hidden example
 @c =============================== Frequent Autoconf Questions, with answers

reply via email to

[Prev in Thread] Current Thread [Next in Thread]