From: Linda Walsh <cygwin@tlinx.org>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: cygwin-bash compat/regression bug... startup line prob
Date: Thu, 01 May 2014 22:11:00 -0000 [thread overview]
Message-ID: <5362C6A0.3040306@tlinx.org> (raw)
Bob McGowan wrote:
> >> Because you weren't running /bin/bash at that point in time, but
> >> /usr/bin/bash. Again, you snipped the relevant portion of your original
> > ----
> > No...I was... the output at the top was from "t.sh", which had
> > #!/bin/bash.
> >
> > But the error message says /usr/bin/bash.
----
That's why I commented that something was bogus. Here it is
again:
law.Bliss> cat /tmp/t.sh
#!/bin/bash -u
echo -e "Hello World\n"
law.Bliss> t.sh
/usr/bin/bash: - : invalid option
Usage: /usr/bin/bash [GNU long option] [option] ...
/usr/bin/bash [GNU long option] [option] script-file ...
GNU long options:
----
The reason the above fails... (I got it to work).. is that if there is a space
on the line after the "-u", that also fails.
I didn't deliberately put one there, but that it no longer handles
separate options is an evolution of software devolution.
But NOTE -- the above error claims it is coming from /usr/bin/bash.
That's not my login shell nor on the shebang line.
That's cygwin-black-magic... converting all /bin paths to /usr/bin...even
shells?...
>
>
> Regarding how your script is executed:
>
> If you do "$ bash t.sh", the she-bang line is *ignored*, it's just a
> comment in this case.
---
I'm aware of that -- I was noting that the alternate ways of invoking it
made a difference. Not that I didn't understand why.
--
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 reply other threads:[~2014-05-01 22:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-01 22:11 Linda Walsh [this message]
2014-05-02 1:33 ` Eric Blake
2014-05-03 19:01 ` Linda Walsh
-- strict thread matches above, loose matches on Subject: below --
2014-04-28 20:43 Linda Walsh
2014-04-28 21:18 ` Eric Blake
2014-05-01 5:57 ` Linda Walsh
2014-05-01 6:41 ` Eric Blake
2014-05-01 18:11 ` 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=5362C6A0.3040306@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).