From: Linda Walsh <cygwin@tlinx.org>
To: cygwin@cygwin.com
Subject: Re: cygwin-bash compat/regression bug... startup line prob
Date: Thu, 01 May 2014 05:57:00 -0000 [thread overview]
Message-ID: <5361E22D.40408@tlinx.org> (raw)
In-Reply-To: <535EC59E.9080602@redhat.com>
Eric Blake wrote:
> On 04/28/2014 02:43 PM, Linda Walsh wrote:
>
> >> cat bin/t.sh
> > #!/bin/bash -u
Um... it doesn't work with 1 argument either.
>
> This is an invalid shebang line. Historically, you are allowed at most
> ONE argument to the program that you will be executing.
?!?
Historically?.. since when? Never encountered that problem on linux
nor on cygwin. This isn't a case of 2 args, just the "-u" by itself
doesn't work.
> > Also weird -- the interp line says "/bin/bash" not "/usr/bin/bash"
> > as the shell, so why does the error come from /usr/bin/bash?
>
> the answer to this question.
---
???
This isn't clear to me. If I am running /bin/bash, why did the error message
say /usr/bin/bash?
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2014-05-01 5:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-28 20:43 Linda Walsh
2014-04-28 21:18 ` Eric Blake
2014-05-01 5:57 ` Linda Walsh [this message]
2014-05-01 6:41 ` Eric Blake
2014-05-01 18:11 ` Linda Walsh
2014-05-01 20:41 ` two execve() inconsistencies [was: cygwin-bash compat/regression bug... startup line prob] Eric Blake
2014-05-02 21:44 ` two execve() inconsistencies (was cygwin-bash compat/regression bug... startup line prob) Linda Walsh
2014-05-01 22:11 cygwin-bash compat/regression bug... startup line prob Linda Walsh
2014-05-02 1:33 ` Eric Blake
2014-05-03 19:01 ` Linda Walsh
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=5361E22D.40408@tlinx.org \
--to=cygwin@tlinx.org \
--cc=cygwin@cygwin.com \
/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).