Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	Wed, 13 Feb 2002 09:52:23 -0500
From:	Chet Ramey <chet AT nike DOT ins DOT cwru DOT edu>
To:	dgluss AT marple-tech DOT com
Subject:	Re: /usr/bin/env - Incorrect parsing of #! line?
Cc:	pjacklam AT online DOT no, cygwin AT cygwin DOT com, chet AT po DOT cwru DOT edu
Reply-To:	chet AT po DOT cwru DOT edu
Message-ID:	<020213145223.AA61562.SM@nike.ins.cwru.edu>
Read-Receipt-To:	chet AT po DOT CWRU DOT Edu
MIME-Version:	1.0
X-In-Reply-To:	Message from dgluss AT marple-tech DOT com of Tue, 12 Feb 2002 17:31:03 -0800 (id <00a201c1b430$5217b5c0$6600a8c0 AT cherry>)

> 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 AT po DOT CWRU DOT 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/

- Raw text -