Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	Thu, 17 Apr 2003 09:26:52 +1000 (EST)
From:	luke DOT kendall AT cisra DOT canon DOT com DOT au
Subject:	Re: Problem in executable file mechanism
To:	lhall AT rfk DOT com
Cc:	"lhall AT pop DOT ma DOT ultranet DOT com" <lhall AT pop DOT ma DOT ultranet DOT com>, cygwin AT cygwin DOT com
In-Reply-To:	<232810-220034316154340659@M2W090.mail2web.com>
MIME-Version:	1.0
Message-Id:	<20030416232653.43E7E34C51@nevin.research.canon.com.au>

On 16 Apr, lhall AT pop DOT ma DOT ultranet DOT 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/

- Raw text -