From: "Daniel Jeliński" <djelinski1@gmail.com>
To: Takashi Yano <takashi.yano@nifty.ne.jp>
Cc: cygwin@cygwin.com
Subject: Re: shebang env sh stopped working with coreutils-8.32-1
Date: Thu, 2 Jun 2022 14:49:00 +0200 [thread overview]
Message-ID: <CAMrH03+XV+e-gZQvGBkPYm3Y+=g_zX7K2qmevwG2-Ho_KdZ5nw@mail.gmail.com> (raw)
In-Reply-To: <20220602173224.900e97413bdeaaff98a2c202@nifty.ne.jp>
Hi Takashi,
Thank you for posting your steps, they helped me solve this issue.
Everything on my end was similar, except that instead of bash
configure I used a custom script that was supposed to prepare the
environment. On closer inspection, it turned out that the script was
downloading make 4.0 and running bash configure with parameter
MAKE=/path/to/make-4.0. After removing that, the build finished
without any issues. It was also much faster than with
cygwin-3.2/make-4.0.
Thanks again,
Daniel
next prev parent reply other threads:[~2022-06-02 12:49 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
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 [this message]
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='CAMrH03+XV+e-gZQvGBkPYm3Y+=g_zX7K2qmevwG2-Ho_KdZ5nw@mail.gmail.com' \
--to=djelinski1@gmail.com \
--cc=cygwin@cygwin.com \
--cc=takashi.yano@nifty.ne.jp \
/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).