configure checking for csh hash hack

[Goldberg, Jon (Jon)]

When used in the context of groff-1.22, the script does the following:

    if echo ./conftest.sh | (csh >/dev/null 2>&1) >/dev/null 2>&1;

On my PC, the script hangs at that line (csh doesn't exit).  Admittedly, its my 
fault: I've modified my .cshrc to do this:

    if ( $?prompt )  exec /bin/bash -i

and removing my hacked .cshrc solves it.  However, wouldn't it be cleaner for 
configure to use the '-f' option to 'csh' and avoid running user .cshrc scripts 
altogether?

regards,
Jon