Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive:	<http://sourceware.cygnus.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help:	<mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
Message-Id:	<200002020547.XAA14530@sunflower.com>
From:	"Doug Wyatt" <dwyatt AT sunflower DOT com>
To:	"Al and Patricia" <carat AT earthlink DOT net>, <cygwin AT sourceware DOT cygnus DOT com>
Date:	Tue, 1 Feb 2000 23:52:44 -0600
MIME-Version:	1.0
Subject:	Re: B.20.1 bash question - paths sent to #!
Reply-to:	dwyatt AT sunflower DOT com
In-reply-to:	<001a01bf6cf8$f1db8d10$da610f0f@fc.hp.com>
X-mailer:	Pegasus Mail for Win32 (v3.12b)

Hi,

I believe I've seen some recent postings about converting pathname
formats - check the archives at <http://sourceware.cygnus.com/ml/cygwin/>.

Quite some time back, I tried using the AS Perl with Cygwin but the final
straw was when I found that AS Perl didn't implement fork and exec.
I'd recommend trying the Cygwin port of Perl; it's fully compatible with
Cygwin and seems very stable.  Look to <http://cygutils.netpedia.net/> if
you want to try it.

Regards,
Doug Wyatt

> Hello -
> 
> I looked in the archives and did not see a solution to this issue:
> 
> I have 3 drives on my NT 4.0 system: C: D: E:.
> I have a perl script that has "#!/usr/bin/perl" in it.
> I am trying to put the perl script in my path, so that I can run it from
> any drive.
> I am using ActiveState Perl.
> 
> Here is the situation.  First, my perl script is called "pop3", and it
> resides in /e/perl/bin.  If I put /e/perl/bin in my path, then I believe
> that bash calls /usr/bin/perl with the file name as /e/perl/bin/pop3.
> However, AS Perl can't interpret this file name and gives a "file not found"
> error.
> 
> I tried putting /perl/bin/ in my path, and this works, as long as I am "on"
> the e drive.  When I go to another drive, /perl/bin does not exist, and
> calling pop3 fails again.
> 
> So what I'd like is to have bash convert the Posix path of the called script
> to win32 when using the #! syntax, so that AS Perl (and other interpreters)
> will have a path it can work with.  Is there a workaround?
> 
> I hope this makes sense.  Let me know if can clarify.
> -----------------
> Al and Patricia
> 
> 
> 
> 
> 
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -