Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sources.redhat.com
Message-ID: <39F8E451.A320EFEB@ece.gatech.edu>
Date: Thu, 26 Oct 2000 22:11:29 -0400
From: "Charles S. Wilson" <cwilson@ece.gatech.edu>
MIME-Version: 1.0
To: Dmitry Epstein <mitia@northwestern.edu>
CC: cygwin@sources.redhat.com
Subject: Re: Running Active Perl scripts in bash
References: <4.3.2.7.2.20001026203036.00b0a990@casbah.it.northwestern.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Here's a workaround:
http://cygutils.netpedia.net/unversioned/perl-contrib/#activestate

This stub executable was contributed by Geoff Hart. His announcement is
quoted below:

-------
In case anyone is interested in using Activestate's Perl distribution
with CYGWIN, I have made a small tool that seems to work. It's a
"perl.exe" executable, which translates the command line arguments from
Cygwin to Win32, then invokes the perl interpreter *directly* from the
Activestate .dll (I didn't want to spawn a subprocess).

Of course, this doesn't fix any file name translation *within* the
running script, so if you need that, this won't work. For example, if
your script accepts file names as input, those paths would need to be
Win32 valid. But it handles \ or / just fine.
-------

--Chuck


Dmitry Epstein wrote:
> 
> 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

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