This is the mail archive of the
mailing list for the Cygwin project.
Re: /usr/bin/env - Incorrect parsing of #! line?
- From: Chet Ramey <chet at nike dot ins dot cwru dot edu>
- To: dgluss at marple-tech dot com
- Cc: pjacklam at online dot no, cygwin at cygwin dot com, chet at po dot cwru dot edu
- Date: Wed, 13 Feb 2002 09:52:23 -0500
- Subject: Re: /usr/bin/env - Incorrect parsing of #! line?
- Read-receipt-to: chet@po.CWRU.Edu
- Reply-to: chet at po dot CWRU dot Edu
> 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@po.CWRU.Edu http://cnswww.cns.cwru.edu/~chet/
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html