Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@sources.redhat.com>
List-Help: <mailto:cygwin-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@sources.redhat.com
Delivered-To: mailing list cygwin@sources.redhat.com
Message-Id: <4.3.2.7.2.20001026203036.00b0a990@casbah.it.northwestern.edu>
X-Sender: dye053@casbah.it.northwestern.edu (Unverified)
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Thu, 26 Oct 2000 20:45:32 -0500
To: cygwin@sources.redhat.com
From: Dmitry Epstein <mitia@northwestern.edu>
Subject: Running Active Perl scripts in bash
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

I know a similar question has been asked a while ago, but I thought perhaps 
there has been some development since then.

I have a problem running Active Perl scripts in bash shell.  I can run 
scripts if I specify the full path to the script (e.g. 
e:/cygwin/usr/local/bin/sw.pl), but not if I just type the name of the 
script (e.g. sw.pl).  Perl gives an error message, something like

Can't open script /usr/local/bin/sw.pl

For some reason, which I can't quite understand, I have no trouble running 
scripts in the current directory.

If I understand correctly, the problem is that bash gives Perl the path 
relative to cygnus mount, which, of course, Perl doesn't understand.  So, 
does anyone know of a work-around, other than installing a cygnus-friendly 
port of Perl?  I would really like to stay with Active Perl, as it is the 
best Windows port around.

Dmitry

Dmitry Epstein
Northwestern University, Evanston, IL.  USA
mitia@northwestern.edu


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

