Mail Archives: cygwin/2001/11/15/14:45:58
Troy,
The interpreter line is already specfied on the first line of all my scripts.
So something else must be the culprit.
Thanks,
Jeff
Troy Noble <troy DOT noble AT channelpoint DOT com> on 11/15/2001 02:35:01 PM
To: Jeff Rozycki/EB/GDYN AT GDYN, cygwin AT cygwin DOT com
cc:
Subject: RE: script-name won't execute but script-name.py will
Try adding
#!/usr/bin/python
as the first line of your scripts (substitute the appropriate
path/filename depending on whether it's python, perl, bash, etc.
and where the filename lives /usr/bin, /usr/local/bin, etc.)
Or if you're sure it's always going to be on your PATH you can use
#!env python
Then the filename extension doesn't matter.
I've even had luck invoking native win32 script interpreters, such as
ActiveState Perl this way such as:
#!/cygdrive/c/Perl/bin/perl
Hey, this stuff really does work like Unix!
Troy
-----Original Message-----
From: JROZYCKI AT ebmail DOT gdeb DOT com [mailto:JROZYCKI AT ebmail DOT gdeb DOT com]
Sent: Thursday, November 15, 2001 12:13 PM
To: cygwin AT cygwin DOT com
Subject: script-name won't execute but script-name.py will
-snip ... you're welcome Earnie
--
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/
- Raw text -