X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-workers-bounces using -f
Date: Wed, 30 Jan 2002 14:40:59 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Tim Van Holder <tim DOT van DOT holder AT pandora DOT be>
cc: djgpp-workers AT delorie DOT com
Subject: Re: Small bash issue with #! handling
In-Reply-To: <000301c1a907$20ea5d60$997c76d5@zastaixp>
Message-ID: <Pine.SUN.3.91.1020130144014.17919M@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Tue, 29 Jan 2002, Tim Van Holder wrote:

> The reason things fail is that our bash handles '#! /bin/sh'
> by looking for sh along the path, and PATH is effectively
> reduced to '.' for the purpose of this test.
> I would suggest that bash should always tack on $DJDIR/bin
> and/or dirname(argv0-of-bash) to PATH for the purpose of
> these lookups (or look in $DJDIR/bin first for any /[s]bin,
> /usr/[s]bin or /usr/local/[s]bin paths).

It sounds wrong to me to make such a global change just to satisfy an
obscure test in a single package.  The current logic of handling
/bin/sh worked for us since v2.01, and we never had any problems.  Why
change it now?

I'd rather try to convince Autoconf maintainers to undo the change
they did for OS/2, and solve the OS/2 problem in some other way.  For
example, they could set SHELL to /bin/sh for OS/2 only.  No one said
DJGPP has to be broken for OS/2's sake.