From: Chet Ramey <chet@nike.ins.cwru.edu>
To: dgluss@marple-tech.com
Cc: pjacklam@online.no, cygwin@cygwin.com, chet@po.cwru.edu
Subject: Re: /usr/bin/env - Incorrect parsing of #! line?
Date: Wed, 13 Feb 2002 06:53:00 -0000 [thread overview]
Message-ID: <020213145223.AA61562.SM@nike.ins.cwru.edu> (raw)
> 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
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next reply other threads:[~2002-02-13 14:53 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-13 6:53 Chet Ramey [this message]
2002-02-13 10:37 ` Christopher Faylor
2002-02-13 11:14 ` Lassi A. Tuura
-- strict thread matches above, loose matches on Subject: below --
2002-02-22 5:26 pjacklam
2002-02-22 1:27 pjacklam
2002-02-22 4:34 ` Michael Schaap
2002-02-13 14:13 Heribert Dahms
2002-02-13 6:50 Chet Ramey
2002-02-13 7:16 ` Gerald S. Williams
2002-02-12 17:47 David Gluss
2002-02-12 17:54 ` Christopher Faylor
2002-02-12 19:10 ` David Gluss
2002-02-13 6:26 ` Gerald S. Williams
2002-02-13 6:38 ` Michael Schaap
2002-02-13 6:39 ` Robert Praetorius
2002-02-13 6:52 ` Benoit Rochefort
2002-02-14 11:55 ` Gerald S. Williams
2002-02-20 12:57 ` Peter J. Acklam
2002-02-20 13:37 ` Larry Hall (RFK Partners, Inc)
2002-02-21 12:47 ` Peter J. Acklam
2002-02-21 13:04 ` Peter J. Acklam
2002-02-21 19:10 ` William F. Hammond
2002-02-20 21:33 ` Christopher Faylor
2002-02-21 13:23 ` Peter J. Acklam
2002-02-12 15:22 Chris January
2002-02-12 10:38 Peter J. Acklam
2002-02-12 10:53 ` Christopher Faylor
2002-02-12 12:16 ` Peter J. Acklam
2002-02-12 14:25 ` Charles Wilson
2002-02-12 14:59 ` David Gluss
2002-02-20 13:03 ` Peter J. Acklam
2002-02-12 11:56 ` David Gluss
2002-02-12 12:17 ` Peter J. Acklam
2002-02-12 13:56 ` David Gluss
2002-02-12 14:57 ` Chris January
2002-02-20 12:57 ` Peter J. Acklam
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=020213145223.AA61562.SM@nike.ins.cwru.edu \
--to=chet@nike.ins.cwru.edu \
--cc=chet@po.cwru.edu \
--cc=cygwin@cygwin.com \
--cc=dgluss@marple-tech.com \
--cc=pjacklam@online.no \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).