I don't think it's worth modifying Autoconf to warn about this. By the time a
new Autoconf version is released, and used to generate source packages
containing configure scripts that are themselves distributed, and these source
packages are built, he problem will no longer be important.
I'm currently having to deal with this sort of thing:
$ ssh random-Red-Hat-host
...
bash: BASH_FUNC_module(): line 0: syntax error near unexpected token `)'
bash: BASH_FUNC_module(): line 0: `BASH_FUNC_module() () { eval
`/usr/bin/modulecmd bash $*`'
bash: error importing function definition for `BASH_FUNC_module'
$
which is caused by a widely-distributed Bash fix that overreacted to the bug and
is causing me more problems than the bug did. Let's not do something like this
with Autoconf.
_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
https://lists.gnu.org/mailman/listinfo/autoconf
