Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Tue, 12 Feb 2002 13:53:10 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: /usr/bin/env - Incorrect parsing of #! line? Message-ID: <20020212185310.GF26027@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <8z9y4kbm DOT fsf AT online DOT no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8z9y4kbm.fsf@online.no> User-Agent: Mutt/1.3.23.1i On Tue, Feb 12, 2002 at 07:38:21PM +0100, Peter J. Acklam wrote: >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. Because... we're mean. cgf -- 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/