[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] Shell function reporting
From: |
Eric Sunshine |
Subject: |
Re: [PATCH] Shell function reporting |
Date: |
Wed, 7 Jan 2004 16:02:38 -0500 |
On 07 Jan 2004 12:33:59 -0800, Paul Eggert wrote:
> Eric Sunshine <address@hidden> 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.
Testing if SHELL is a "desirable" shell is not necessarily a bug, but
assuming that SHELL is the shell running the script certainly is a bad bug.
> 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.
> Thanks very much for pursuing this. Will your patch take the Autoconf
> 2.59 approach for testing the current shell?
Yes, the new patch first checks the currently running shell. If that fails,
then it checks SHELL, since SHELL might reference a suitable shell. Finally,
if that fails, then it performs the more exhaustive search for an
appropriate shell.
-- ES