From: "Daniel Jeliński" <djelinski1@gmail.com>
To: Ken Brown <kbrown@cornell.edu>
Cc: cygwin@cygwin.com
Subject: Re: shebang env sh stopped working with coreutils-8.32-1
Date: Wed, 1 Jun 2022 15:29:34 +0200 [thread overview]
Message-ID: <CAMrH03LbwFMvmsONC4_mswRwc+0+MYpuJRkfR-GUK6HmMcE2iQ@mail.gmail.com> (raw)
In-Reply-To: <da6669b3-40c4-67b1-f883-8f310febdd2e@cornell.edu>
Hi Ken,
Thanks for checking.
You're right, I'm still on cygwin 3.2.0 because of issues with running
make (see "GNU make losing jobserver tokens").
Tested with cygwin-3.3.5 and env seems to work.
Sorry for the noise.
Regards,
Daniel
śr., 1 cze 2022 o 15:03 Ken Brown <kbrown@cornell.edu> napisał(a):
>
> On 6/1/2022 8:33 AM, Daniel Jeliński wrote:
> > Hi all,
> > As the title says. To reproduce:
> > - create a file (test.sh) with the following contents:
> >
> > #!/usr/bin/env sh
> > echo success
> >
> > - make it executable (chmod a+x test.sh)
> > - execute (./test.sh)
> >
> > With coreutils-8.26-2 the script prints "success". With
> > coreutils-8.32-1 and 9.1-1 nothing happens.
>
> Works for me.
>
> $ cat test.sh
> #!/usr/bin/env sh
> echo success
>
> $ ./test.sh
> success
>
> $ cygcheck -cd coreutils
> Cygwin Package Information
> Package Version
> coreutils 8.32-1
>
> There must be something else going on in your environment.
>
> Ken
>
> --
> Problem reports: https://cygwin.com/problems.html
> FAQ: https://cygwin.com/faq/
> Documentation: https://cygwin.com/docs.html
> Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2022-06-01 13:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 12:33 Daniel Jeliński
2022-06-01 13:01 ` Ken Brown
2022-06-01 13:29 ` Daniel Jeliński [this message]
2022-06-01 16:21 ` Ken Brown
2022-06-01 19:38 ` Daniel Jeliński
2022-06-02 8:32 ` Takashi Yano
2022-06-02 12:49 ` Daniel Jeliński
2022-06-02 14:02 ` Ken Brown
2022-06-03 12:35 ` Ken Brown
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=CAMrH03LbwFMvmsONC4_mswRwc+0+MYpuJRkfR-GUK6HmMcE2iQ@mail.gmail.com \
--to=djelinski1@gmail.com \
--cc=cygwin@cygwin.com \
--cc=kbrown@cornell.edu \
/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).