Issue in autoconf with config.status generation

[Evan Hunter]

Hi,

I have found what I think is an issue with autoconf, involving the generation 
of config.status.

As I understand it, the 'config.status --recheck' command is supposed re-run 
the configure script using all the same options as it was originally run with.
The problem I'm finding is that the command-line options are being saved in the 
config.status, but not the environment variables.

In the following sequence of commands, the last one will fail since it has not 
been saved in the config.status file:

autoreconf --install --verbose --force
CRITICAL_VARIABLE=ok ./configure

./config.status --recheck

This is a problem because in some packages, the makefile calls autoreconf, then 
'config.status --recheck'  during a make, so if the autoconf or configure 
scripts have been touched, then 'config.status --recheck'  will be called. It 
will fail to build at this point if the user originally configured things like 
PKG_CONFIG_PATH one-time temporary environment variables.

I have made a small set of autoconf scripts which illustrate the problem (see 
attached). Just extract then run './demo'.

Also attached is the testsuite.log file from my build of autoconf.

Regards,

Evan Hunter

testsuite.log
Description: testsuite.log

fault_example.tar.bz2
Description: fault_example.tar.bz2