delorie.com/archives/browse.cgi | search |
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 |
Message-ID: | <00a201c1b430$5217b5c0$6600a8c0@cherry> |
From: | "David Gluss" <dgluss AT marple-tech DOT com> |
To: | "Peter J. Acklam" <pjacklam AT online DOT no> |
Cc: | <cygwin AT cygwin DOT com> |
Subject: | Re: /usr/bin/env - Incorrect parsing of #! line? |
Date: | Tue, 12 Feb 2002 17:31:03 -0800 |
MIME-Version: | 1.0 |
X-Priority: | 3 |
X-MSMail-Priority: | Normal |
X-Mailer: | Microsoft Outlook Express 6.00.2600.0000 |
X-MimeOLE: | Produced By Microsoft MimeOLE V6.00.2600.0000 |
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? DG -- 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/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |