This is the mail archive of the cygwin@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Problem in executable file mechanism


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/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]