This is the mail archive of the cygwin 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: Problems with Indirect Interpretation (#!/bin/csh, #!/bin/tcsh, #!/bin/perl, etc...)


> -----Original Message-----
> From: cygwin-owner On Behalf Of Rocket Boy
> Sent: 11 May 2004 18:03

> I have recently installed cygwin on my PC at home
> (Win-XP) and at work (Win-NT). I can't seem to get
> indirect interpretation (e.g. #!/bin/csh -f,
> #!/bin/tcsh -f, etc...) to work in either location. I
> have tried it in different shells: bash, tcsh, and sh.
> And, with different interpreters: #!/bin/bash,
> #!/bin/csh, #!/bin/tcsh, #!/bin/sh,
> #!/bin/perl ,etc... I have verified that the files are
> executable (777) and are in the directory that I am
> trying to execute them from. Regardless of the
> combination I get a message like:
>  
> bash: test.pl: command not found
>  
> or
>  
> bash: test.sh: command not found

  Betcha don't have . in your $PATH.  Which is as it should be.  Try
executing the commands like this:

./test.pl
./test.sh

  There's something in the FAQ about this.  Ah, yes, here we go:

http://cygwin.com/faq/faq_4.html#SEC36

    cheers, 
      DaveK
-- 
Can't think of a witty .sigline today....


--
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]