autoconf-patches
[Top][All Lists]
Advanced

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

[Autoconf-patches] Checking stderr from configure


From: Pavel Roskin
Subject: [Autoconf-patches] Checking stderr from configure
Date: Tue, 19 Sep 2000 20:53:49 -0400 (EDT)

Hello!

It looks like I have overestimated the complexity of the problem with
checking for shell errors in the testsuite. It's already done :-)

The reasons for excluding AC_PREFIX_PROGRAM and AC_F77_FUNC from dumb
testing without arguments are valid - they haven't been written to operate
this way.

Individual tests will be written later, but now those two macros just
stand in the way. It's extremely important to catch all shell errors where
we don't expect them to be.

Regards,
Pavel Roskin

================================
Index: ChangeLog
--- ChangeLog   Tue Sep 19 17:23:25 2000
+++ ChangeLog   Tue Sep 19 20:22:17 2000
@@ -0,0 +1,7 @@
+2000-09-19  Pavel Roskin  <address@hidden>
+
+       * tests/Makefile.am: AC_PREFIX_PROGRAM and AC_F77_FUNC excluded
+       from testing because they require an argument.
+       * tests/atspecific.m4: Make sure that configure doesn't write
+       anything to stderr.
+
Index: tests/Makefile.am
--- tests/Makefile.am   Tue Sep 19 14:17:34 2000
+++ tests/Makefile.am   Tue Sep 19 19:59:09 2000
@@ -47,8 +47,8 @@
 # and some are already tested elsewhere.  EGREP_EXCLUDE must filter out
 # the macros we don't want to test in syntax.m4.
 #
-# - AC_CANONICALIZE
-#   Needs an argument.
+# - AC_CANONICALIZE, AC_PREFIX_PROGRAM
+#   Need an argument.
 # - AC_CHECK decl, file, func, header, lib, member, prog, sizeof, type
 #   Performed in the semantics tests.
 # - AC_CONFIG
@@ -58,7 +58,7 @@
 #   infinite m4 recursion if AC_INIT it used twice.
 # - AC_LANG*
 #   Heavily used by other macros.
-# - AC_PATH_PROGS?
+# - AC_PATH_PROGS?, AC_F77_FUNC
 #   They produce `= val' because $1, the variable used to store the result,
 #   is empty.
 # - AC_TRY, AC_.*_IFELSE
@@ -81,6 +81,7 @@
 ^AC_CANONICALIZE$$\
 ^AC_CHECK_(DECL|FILE|FUNC|HEADER|LIB|MEMBER|PROG|SIZEOF|TOOL|TYPE)S?$$\
 ^AC_CONFIG\
+^AC_F77_FUNC$$\
 ^AC_INIT\
 ^AC_LANG\
 ^AC_LINKER_OPTION$$\
@@ -88,6 +89,7 @@
 ^AC_LIST_MEMBER_OF$$\
 ^AC_OUTPUT$$\
 ^AC_PATH_(TOOL|PROG)S?$$\
+^AC_PREFIX_PROGRAM$$\
 ^AC_REPLACE_FUNCS$$\
 ^AC_SEARCH_LIBS$$\
 ^AC_TRY\
Index: tests/atspecific.m4
--- tests/atspecific.m4 Tue Sep 19 14:18:29 2000
+++ tests/atspecific.m4 Tue Sep 19 18:34:42 2000
@@ -97,7 +97,7 @@
 dnl lines, so grepping -v warning is not enough.
 AT_CHECK([autoconf --autoconf-dir .. -l $at_srcdir], 0,, ignore)
 AT_CHECK([autoheader --autoconf-dir .. -l $at_srcdir], 0,, ignore)
-AT_CHECK([top_srcdir=$top_srcdir ./configure], 0, ignore, ignore)
+AT_CHECK([top_srcdir=$top_srcdir ./configure], 0, ignore, [])
 test -n "$at_verbose" && echo "--- config.log" && cat config.log
 
 dnl Some tests might exit prematurely when they find a problem, in
================================




reply via email to

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