Hello,
I noticed that AS_UNSET uses export at the end. So we have
$as_unset ac_configure_args0 ||
test "${ac_configure_args0+set}" != set ||
{ ac_configure_args0=; export ac_configure_args0; }
I do not think the export makes sense. When unset is not available
and the variable is set, it is enough to set the neutralizing value.
If the variable was not exported, then child processes will not get
it, which is as good as if it was unset. If the variable was
exported, the export is redundant.
What about the following patch?
Have a nice day,
Stepan
2007-08-22 Stepan Kasal <[EMAIL PROTECTED]>
* lib/m4sugar/m4sh.m4 (AS_UNSET): Do not call export the
variable when the neutralizing value is used.
Index: lib/m4sugar/m4sh.m4
===================================================================
RCS file: /cvsroot/autoconf/autoconf/lib/m4sugar/m4sh.m4,v
retrieving revision 1.209
diff -u -r1.209 m4sh.m4
--- lib/m4sugar/m4sh.m4 20 Jul 2007 23:11:54 -0000 1.209
+++ lib/m4sugar/m4sh.m4 22 Aug 2007 11:57:48 -0000
@@ -542,7 +542,7 @@
# VALUE-IF-UNSET-NOT-SUPPORTED. `as_unset' must have been computed.
m4_defun([AS_UNSET],
[AS_REQUIRE([_AS_UNSET_PREPARE])dnl
-$as_unset $1 || test "${$1+set}" != set || { $1=$2; export $1; }])
+$as_unset $1 || test "${$1+set}" != set || $1=$2])
