From: "David Gluss" <dgluss@marple-tech.com>
To: <cygwin@cygwin.com>, "Peter J. Acklam" <pjacklam@online.no>
Subject: Re: /usr/bin/env - Incorrect parsing of #! line?
Date: Tue, 12 Feb 2002 11:56:00 -0000 [thread overview]
Message-ID: <001b01c1b3ff$46981950$6600a8c0@cherry> (raw)
In-Reply-To: <8z9y4kbm.fsf@online.no>
I don't know if it's constructive to suggest an alternative trick, rather
than trying to fix cygwin, in this forum. However, this might work
for you:
>------------
>: # -*-Mode: perl;-*- use perl, wherever it is
>eval 'exec perl -wS $0 ${1+"$@"}'
> if 0;
>#!/usr/local/bin/perl -w
>------------
DG
----- Original Message -----
From: "Peter J. Acklam" <pjacklam@online.no>
To: <cygwin@cygwin.com>
Sent: Tuesday, February 12, 2002 10:38 AM
Subject: /usr/bin/env - Incorrect parsing of #! line?
> I use different computers where Perl is installed different
> places, so I can't hardcode the location of perl in the shebang
> line. Thus, I use env, which works great on all UNIXes I work on,
> for instance
>
> #!/usr/bin/env perl -w
>
> print "This is Perl version $]\n";
>
> but on Cygwin I get
>
> /usr/bin/env: perl -w: No such file or directory
>
> why does Cygwin look for the file "perl -w". No UNIX I have
> worked on would parse the shebang line that way.
>
> Peter
>
> --
> People say I'm indifferent, but I don't care.
>
>
> --
> 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/
>
--
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/
next prev parent reply other threads:[~2002-02-12 19:56 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-12 10:38 Peter J. Acklam
2002-02-12 10:53 ` Christopher Faylor
2002-02-12 12:16 ` Peter J. Acklam
2002-02-12 14:25 ` Charles Wilson
2002-02-12 14:59 ` David Gluss
2002-02-20 13:03 ` Peter J. Acklam
2002-02-12 11:56 ` David Gluss [this message]
2002-02-12 12:17 ` Peter J. Acklam
2002-02-12 13:56 ` David Gluss
2002-02-12 14:57 ` Chris January
2002-02-20 12:57 ` Peter J. Acklam
2002-02-12 15:22 Chris January
2002-02-12 17:47 David Gluss
2002-02-12 17:54 ` Christopher Faylor
2002-02-12 19:10 ` David Gluss
2002-02-13 6:26 ` Gerald S. Williams
2002-02-13 6:38 ` Michael Schaap
2002-02-13 6:39 ` Robert Praetorius
2002-02-13 6:52 ` Benoit Rochefort
2002-02-14 11:55 ` Gerald S. Williams
2002-02-20 12:57 ` Peter J. Acklam
2002-02-20 13:37 ` Larry Hall (RFK Partners, Inc)
2002-02-21 12:47 ` Peter J. Acklam
2002-02-21 13:04 ` Peter J. Acklam
2002-02-21 19:10 ` William F. Hammond
2002-02-20 21:33 ` Christopher Faylor
2002-02-21 13:23 ` Peter J. Acklam
2002-02-13 6:50 Chet Ramey
2002-02-13 7:16 ` Gerald S. Williams
2002-02-13 6:53 Chet Ramey
2002-02-13 10:37 ` Christopher Faylor
2002-02-13 11:14 ` Lassi A. Tuura
2002-02-13 14:13 Heribert Dahms
2002-02-22 1:27 pjacklam
2002-02-22 4:34 ` Michael Schaap
2002-02-22 5:26 pjacklam
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='001b01c1b3ff$46981950$6600a8c0@cherry' \
--to=dgluss@marple-tech.com \
--cc=cygwin@cygwin.com \
--cc=pjacklam@online.no \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).