Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <007301c1b418$ec8aaad0$0100a8c0@advent02> From: "Chris January" To: "Peter J. Acklam" Cc: References: <8z9y4kbm.fsf@online.no> Subject: Re: /usr/bin/env - Incorrect parsing of #! line? Date: Tue, 12 Feb 2002 22:59:26 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 > 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. Linux parses things this way too. I don't know what "UNIX"'s this works on. (Sun, HP?) Regards Chris -- 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/