>> fi >> AS_EXIT(1)])]) >> +else >> + SHELL=$CONFIG_SHELL >> fi > > Not sure about this one. It is not wrong to pass SHELL down, but > typically, inside the generated scripts you still won't be able to rely > on its value. config.status for example is called from Makefiles as > well, not just from configure. > > Or maybe I have misunderstood the intent of this patch?
The subject is misleading; the intent of this patch is just to make sure that the #! $SHELL is right in the config.status script, matching the shell in which config.status is supposed to run. CONFIG_SHELL is "passed down" in the sense that it is present in the file. Paolo
