From: "Mark E." <snowball3 AT bigfoot DOT com>
To: DJGPP Workers <djgpp-workers AT delorie DOT com>
Date: Tue, 23 May 2000 16:50:13 -0400
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: __dosexec_find_on_path question
Message-ID: <392AB6C5.30256.2B47D6@localhost>
X-mailer: Pegasus Mail for Win32 (v3.12c)
Reply-To: djgpp-workers AT delorie DOT com

> I've been using __dosexec_find_on_path in my Bash 2.04 beta to find disk 
> commands. But when LFN is available, a search for "autoconf" will return 
> "autoconf.sh" when both "autoconf" and "autoconf.sh" are both in the same 
> directory in a PATH. This causes 'spawnve (P_WAIT, "autoconf", args, env)' to 
> execute autoconf.sh instead of autoconf. Is this the way it's supposed to 
> work? Looks like I'll have to make some changes to Bash 2.04 to prevent this.

The comments in dosexec.c say that this is the way it does work, but in this 
narrow case it does seem wrong.