Update of sr #110283 (project autoconf):
Status: None => Ready For Test
_______________________________________________________
Follow-up Comment #1:
It appears that many of the failures are spurious, caused by ksh93's
_AST_FEATURES shell variable varying from invocation to invocation. The test
suite already filters out many other shell variables with this property.
Could you please apply the following patch and report how many failures
remain?
diff --git a/tests/local.at b/tests/local.at
index 308eae32..e8302273 100644
--- a/tests/local.at
+++ b/tests/local.at
@@ -326,6 +326,7 @@ m4_define([AT_CHECK_CONFIGURE],
# - AC_SUBST'ed variables
# (FIXME: Generate a list of these automatically.)
# - _|@|.[*#?$].|argv|ARGC|LINENO|OLDPWD|PIPESTATUS|RANDOM|SECONDS
+# |_AST_FEATURES
# Some variables some shells use and change.
# `.[*#?$].' catches `$#' etc. which are displayed like this:
# | '!'=18186
@@ -375,7 +376,8 @@ if test -f state-env.before && test -f state-env.after;
then
[AWK|LEX|LEXLIB|LEX_OUTPUT_ROOT|LN_S|M4|MKDIR_P|RANLIB|SET_MAKE|YACC],
[GREP|[EF]GREP|SED],
[[_@]|.[*#?$].],
-
[argv|ARGC|LINENO|BASH_ARGC|BASH_ARGV|OLDPWD|PIPESTATUS|RANDOM|SECONDS]))=' \
+ [argv|ARGC|LINENO|BASH_ARGC|BASH_ARGV|OLDPWD|PIPESTATUS|RANDOM],
+ [SECONDS|_AST_FEATURES]))=' \
$act_file ||
test $? -eq 1 || echo failed >&2
) 2>stderr-$act_file |
It would also be helpful if you could file a separate bug report explaining
what is wrong with ksh93's 'rm -f' and how it makes configure fail. We ought
to be detecting the problem and working around it; CONFIG_SHELL=/usr/bin/bash
shouldn't be necessary.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/support/?110283>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
