This is the mail archive of the
mailing list for the Cygwin project.
Re: /usr/bin/env - Incorrect parsing of #! line?
Hmm. You're right about that. In that case I will do nothing.
Of course I've always objected to that behavior...but so it is.
----- Original Message -----
From: "Christopher Faylor" <email@example.com>
Sent: Tuesday, February 12, 2002 5:54 PM
Subject: Re: /usr/bin/env - Incorrect parsing of #! line?
> 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.
> 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/
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html