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 21:38:53 +0200 [thread overview]
Message-ID: <CAMrH03LAR_kjDCxBstS39MGgKsr55q4v42cx5oegy=1-5Mycyg@mail.gmail.com> (raw)
In-Reply-To: <8239fa91-e061-7ae2-d077-8343b8c243d4@cornell.edu>
śr., 1 cze 2022 o 18:21 Ken Brown <kbrown@cornell.edu> napisał(a):
>
> On 6/1/2022 9:29 AM, Daniel Jeliński wrote:
> > You're right, I'm still on cygwin 3.2.0 because of issues with running
> > make (see "GNU make losing jobserver tokens").
>
> The original report on that issue
> (https://cygwin.com/pipermail/cygwin/2022-March/251095.html) described it as
> long-standing. Are you saying that it got worse with cygwin-3.3.x? That would
> be disappointing, because we overhauled the internal implementation of pipes in
> cygwin-3.3.0.
Yessir. I'm also using Cygwin to build OpenJDK. With Cygwin 3.2.0, the
build starts with 8 threads and usually loses no more than 1-2 tokens;
with 3.3.5 the build either finishes with a single token, or segfaults
after a few seconds.
FWIW, I haven't seen any problems with single-threaded builds.
Regards,
Daniel
next prev parent reply other threads:[~2022-06-01 19:39 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 [this message]
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='CAMrH03LAR_kjDCxBstS39MGgKsr55q4v42cx5oegy=1-5Mycyg@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).