On 5/19/2010 8:50 AM, Rockefeller, Harry wrote: > Given that 'foo' is a bash script, why is it that: > > $ foo > > returns the error: > > bash: ./bin/foo: No such file or directory
What happens when you directly run ./bin/foo? What is the shebang (first line) of foo? > BUT since foo is *really in* PATH, e.g., > > $ `which foo` > > runs correctly? What is the output of "which foo" in this case? -Jeremy -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
