From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5810 invoked by alias); 22 Feb 2002 08:53:08 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Received: (qmail 5657 invoked from network); 22 Feb 2002 08:53:03 -0000 Received: from unknown (HELO mail49.fg.online.no) (148.122.161.49) by sources.redhat.com with SMTP; 22 Feb 2002 08:53:03 -0000 Received: from epostleser.online.no (epostleser12.frisurf.no [148.122.3.20]) by mail49.fg.online.no (8.9.3/8.9.3) with ESMTP id JAA20525 for ; Fri, 22 Feb 2002 09:53:01 +0100 (MET) X-WebMail-UserID: pjacklam@online.no Date: Fri, 22 Feb 2002 01:27:00 -0000 From: pjacklam To: cygwin@cygwin.com X-EXP32-SerialNo: 50000140 Subject: Re: /usr/bin/env - Incorrect parsing of #! line? Message-ID: <3C765D91@epostleser.online.no> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-Mailer: InterChange (Hydra) SMTP v3.62 X-SW-Source: 2002-02/txt/msg01092.txt.bz2 hammond@csc.albany.edu (William F. Hammond) writes: > I don't understand why you want to use /usr/bin/env > under Cygwin. The reason is portability. I have written hundreds of Perl utilities which I find extremely useful and I want them to run smoothly both on UNIX and cygwin. I really hesitate to maintain one set of utilities for cygwin, one for Solaris, one for HP-UX, etc. > Not everything that makes sense under *ix makes sense > for Cygwin. I know, but cygwin respects shebang lines (e.g., a text file in the path starting with the line "#!/bin/gawk" will really be run by gawk), so I'm sure there is a way to get this working right. I just haven't found it yet. > Presumably one runs Cygwin because one does not want > to run Linux so that one can have simultaneous single > platform access to Win* things and Gnu things familiar > in *ix contexts. Yep. > That said, doesn't it then make sense to use a straight > Win* build for perl so that perl can be used in Win* > mode? I have tried, and I found out that a Win* build of Perl doesn't integrate well with cygwin. > Granted that -- and granted the desire to build > environment outside of the Perl script itself -- one > may use either a bat file or an sh script, as appropriate > for the calling context, to create the needed environment. True, that works, I have tried, but then I need a whole set of bat files and sh files in addition to the original Perl scripts and that's what I am trying to avoid. :-) Thanks for your input! Peter -- 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/