From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Subject: Re: shebang env sh stopped working with coreutils-8.32-1
Date: Thu, 2 Jun 2022 17:32:24 +0900 [thread overview]
Message-ID: <20220602173224.900e97413bdeaaff98a2c202@nifty.ne.jp> (raw)
In-Reply-To: <CAMrH03LAR_kjDCxBstS39MGgKsr55q4v42cx5oegy=1-5Mycyg@mail.gmail.com>
On Wed, 1 Jun 2022 21:38:53 +0200
Daniel Jeliński wrote:
> śr., 1 cze 2022 o 18:21 Ken Brown <kbrown@cornell.edu> napisał(a):
> > 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.
How can we reproduce the losing jobserver token issue?
I tried the following steps, however, no such messages appeared.
1) git clone https://git.openjdk.java.net/jdk/
2) cd jdk
3) export TEMP=/tmp
4) bash configure
5) make images
The summary of the configuration is as follows:
Configuration summary:
* Name: windows-x86_64-server-release
* Debug level: release
* HS debug level: product
* JVM variants: server
* JVM features: server: 'cds compiler1 compiler2 epsilongc g1gc jfr jni-check jvmci jvmti management parallelgc serialgc services shenandoahgc vm-structs zgc'
* OpenJDK target: OS: windows, CPU architecture: x86, address length: 64
* Version string: 19-internal-adhoc.yano.jdk (19-internal)
* Source date: Determined at build time
Tools summary:
* Environment: cygwin version 3.3.5-341.x86_64, 2022-05-13 12:27 UTC; windows version 10.0.19044.1706; prefix "/cygdrive"; root "C:\cygwin64"
* Boot JDK: java version "18" 2022-03-22 Java(TM) SE Runtime Environment (build 18+36-2087) Java HotSpot(TM) 64-Bit Server VM (build 18+36-2087, mixed mode, sharing) (at /cygdrive/c/progra~1/java/jdk-18)
* Toolchain: microsoft (Microsoft Visual Studio 2022)
* C Compiler: Version 19.32.31329 (at /cygdrive/c/progra~1/micros~1/2022/commun~1/vc/tools/msvc/1432~1.313/bin/hostx86/x64/cl.exe)
* C++ Compiler: Version 19.32.31329 (at /cygdrive/c/progra~1/micros~1/2022/commun~1/vc/tools/msvc/1432~1.313/bin/hostx86/x64/cl.exe)
Build performance summary:
* Build jobs: 8
* Memory limit: 16136 MB
$ cygcheck -c autoconf make zip unzip
Cygwin Package Information
Package Version Status
autoconf 15-1 OK
make 4.3-1 OK
unzip 6.0-17 OK
zip 3.0-12 OK
--
Takashi Yano <takashi.yano@nifty.ne.jp>
next prev parent reply other threads:[~2022-06-02 8:33 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 [this message]
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=20220602173224.900e97413bdeaaff98a2c202@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--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).