Eric Sunshine <[EMAIL PROTECTED]> writes: > in my environment, SHELL is set to tcsh, yet when I invoke > configure, it is run by /bin/sh (because of #! /bin/sh at the top of > the script).
Ouch (and I should have figured that out myself, sorry). Hence it's a serious bug to test $SHELL at all. Autoconf 2.59 doesn't have this bug, as it tests the current shell directly, by running some code in it, rather than by trying to invoke $SHELL. > I have already prepared a much more comprehensive patch which > addresses these problems, plus the problem of Autoconf CVS choosing > a less functional shell over a more functional shell. I will be > submitting this new patch shortly. Thanks very much for pursuing this. Will your patch take the Autoconf 2.59 approach for testing the current shell?
