This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: /usr/bin/env - Incorrect parsing of #! line?
- From: Christopher Faylor <cgf at redhat dot com>
- To: cygwin at cygwin dot com
- Date: Tue, 12 Feb 2002 20:54:00 -0500
- Subject: Re: /usr/bin/env - Incorrect parsing of #! line?
- References: <00a201c1b430$5217b5c0$6600a8c0@cherry>
- Reply-to: cygwin at cygwin dot com
On Tue, Feb 12, 2002 at 05:31:03PM -0800, David Gluss wrote:
>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?
I think you're misinterpreting the problem. If it works the same way
on linux and on cygwin, then there is nothing to fix.
cgf
--
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/