From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28985 invoked by alias); 13 Feb 2002 14:53:36 -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 28838 invoked from network); 13 Feb 2002 14:53:31 -0000 Received: from unknown (HELO opus.INS.cwru.edu) (129.22.8.2) by sources.redhat.com with SMTP; 13 Feb 2002 14:53:31 -0000 Received: from nike.ins.cwru.edu (nike.INS.CWRU.Edu [129.22.8.219]) by opus.INS.cwru.edu with SMTP (8.11.6+cwru/CWRU-3.9) id g1DErR021972; Wed, 13 Feb 2002 09:53:27 -0500 (EST) (from chet@nike.ins.cwru.edu) Date: Wed, 13 Feb 2002 06:53:00 -0000 From: Chet Ramey To: dgluss@marple-tech.com Subject: Re: /usr/bin/env - Incorrect parsing of #! line? Cc: pjacklam@online.no, cygwin@cygwin.com, chet@po.cwru.edu Reply-To: chet@po.CWRU.Edu Message-ID: <020213145223.AA61562.SM@nike.ins.cwru.edu> Read-Receipt-To: chet@po.CWRU.Edu MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-In-Reply-To: Message from dgluss@marple-tech.com of Tue, 12 Feb 2002 17:31:03 -0800 (id <00a201c1b430$5217b5c0$6600a8c0@cherry>) X-SW-Source: 2002-02/txt/msg00658.txt.bz2 > The problem looks to be that bash "helps out" the system > by executing scripts beginning with #!. In the source for > bash, look in execute_cmd.c, line 3369. Only one argument > is allowed. So e.g. #!/usr/bin/env perl -w becomes > "/usr/bin/env" "perl -w" > If I make a patch for this, should it go to the cygwin list? > Should it just go to gnu.bash.bug and leave it at that? Only if the kernel doesn't do it, as discovered by configure. Virtually all Unices understand that executable format in the kernel. Cygwin does, too. -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ( ``Discere est Dolere'' -- chet) Chet Ramey, CWRU chet@po.CWRU.Edu http://cnswww.cns.cwru.edu/~chet/ -- 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/