Re: testsuite -C dir

[Eric Blake-1]

> > -   eval "$at_envvar='$at_value'"
> > +   # Export now, but save eval for later and for debug scripts.
> >     export $at_envvar
> 
> Does Autotest (now that it uses shell functions) still cater to shells
> that need to re-export variables after changing them?  Then
> at_debug_args should contain the export statements, too.

The way I read the autoconf manual, you are required to export
any variable that you modify and want child processes to see
(in case the variable began life inherited into the current environment);
and this is still valid on existing systems (think Solaris /bin/sh).
But I see nothing that places an order on the export.  In other words,
does anyone know of a shell where doing the export first fails?

For reference, I tested Solaris 8 /bin/sh:

$ foo=bar /bin/sh -c 'foo=blah; /bin/sh -c '\''echo $foo'\'
bar
$ foo=bar /bin/sh -c 'foo=blah; export foo; /bin/sh -c '\''echo $foo'\'
blah
$ foo=bar /bin/sh -c 'export foo; foo=blah; /bin/sh -c '\''echo $foo'\'
blah

-- 
Eric Blake

-- 
View this message in context: 
http://www.nabble.com/testsuite--C-dir-tp15115560p15163615.html
Sent from the Gnu - Autoconf - Patches mailing list archive at Nabble.com.