it was deliberate that it would not see this variable upon the
recheck.
OTOH, setting CONFIG_SHELL upon `./config.status --recheck' makes a
certain assumption: that the shell does not change. Or, for example,
the PATH, should the user not have used an absolute path as in
CONFIG_SHELL=bash bash configure
Ralf Wildenhues [EMAIL PROTECTED] writes:
One possibility would be to restart once with /bin/sh, or, if part of
the environment, with CONFIG_SHELL, or, after parsing the command line,
with CONFIG_SHELL, if that is given there. All of this is very slow
(read: dog-slow), and I'd really like to
