This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: script-name won't execute but script-name.py will
- From: David Starks-Browning <starksb at ebi dot ac dot uk>
- To: JROZYCKI at ebmail dot gdeb dot com
- Cc: cygwin at cygwin dot com
- Date: Fri, 16 Nov 2001 14:39:28 +0000
- Subject: Re: script-name won't execute but script-name.py will
- References: <85256B06.004FB339.00@groton5.notes.gdeb.com>
On Friday 16 Nov 01, JROZYCKI@ebmail.gdeb.com writes:
> Pavel,
> We are on NT 4.0. I believe I have proper permissions because I can run the
> script when I tack on the script's extension, such as pl or awk. The response
> is "command not found", not permission denied... Here is some output:
>
> bin $ pwd
> /home/jrozycki/bin
> bin $ ll
> total 51
> drwxr-xr-x 5 jrozycki users 4096 Nov 15 19:09 ./
> drwxr-xr-x 10 jrozycki users 8192 Nov 15 15:55 ../
> -rwxr-xr-x 1 jrozycki users 735 Nov 15 14:41 maxcom.py*
> <snip>
> bin $ maxcom
> bash: maxcom: command not found
It sounds like bash cannot locate the interpreter -- the thing in the
line
#! /path/to/interpreter
But you don't tell us what you have there so it is hard to say
anything more.
The relevant FAQ entry is "Why doesn't my shell script work?".
Regards,
David
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/