Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Thu, 17 Apr 2003 09:26:52 +1000 (EST)
From: luke.kendall@cisra.canon.com.au
Subject: Re: Problem in executable file mechanism
To: lhall@rfk.com
Cc: "lhall@pop.ma.ultranet.com" <lhall@pop.ma.ultranet.com>, cygwin@cygwin.com
In-Reply-To: <232810-220034316154340659@M2W090.mail2web.com>
MIME-Version: 1.0
Content-Type: TEXT/plain; CHARSET=US-ASCII
Message-Id: <20030416232653.43E7E34C51@nevin.research.canon.com.au>

On 16 Apr, lhall@pop.ma.ultranet.com wrote:
>  OK, what are you seeing?  I get "bash: ls: command not found" with  
>  1.3.20 and 1.3.22. 

Yes, that's what I get.  For two other native Windows commands, it
failed silently, yet for other native Windows commands, it also failed
with a "command not found" message.  Puzzling.

IIRC, when I had a little more time, about a month ago, I think I also
ran the whole invoking shell inside strace (ouch), which was what led
me to discover the directory-executable name clash.  Up till then, I
just had a mystery that one command on my path wouldn't execute from
Cygwin, and wouldn't report any kind of error.

HTH,

luke


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/