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
From:	"Gerald S. Williams" <gsw AT agere DOT com>
To:	<cygwin AT cygwin DOT com>
Cc:	<dgluss AT marple-tech DOT com>, <pjacklam AT online DOT no>, <chet AT po DOT cwru DOT edu>
Subject:	RE: /usr/bin/env - Incorrect parsing of #! line?
Date:	Wed, 13 Feb 2002 10:15:44 -0500
Message-ID:	<GBEGLOMMCLDACBPKDIHFKEPKCGAA.gsw@agere.com>
MIME-Version:	1.0
X-Priority:	3 (Normal)
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance:	Normal
In-Reply-To:	<020213144737.AA61530.SM@nike.ins.cwru.edu>
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4807.1700

If DG's assessment is correct:

> 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?

Then it's a BASH issue. Some flavors of UNIX do this in the
kernel. If this is the case for CYGWIN, then it is a CYGWIN
issue as well. Either way, it sounds like DG has a pretty
good handle on this issue.

-O Gerald S. Williams, 22Y-103GA : mailto:gsw AT agere DOT com O-
-O AGERE SYSTEMS, 555 UNION BLVD : office:610-712-8661  O-
-O ALLENTOWN, PA, USA 18109-3286 : mobile:908-672-7592  O-


--
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 -