From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Subject: Re: Cygwin 3.3.0 regression: "make" segmentation faults
Date: Tue, 16 Nov 2021 17:11:13 +0900 [thread overview]
Message-ID: <20211116171113.8a284ca48adcefbb0f90fac7@nifty.ne.jp> (raw)
In-Reply-To: <5b61de48-0d57-38fb-4997-20f55a20030f@redhat.com>
On Mon, 15 Nov 2021 17:47:58 +0100
Aleksey Shipilev wrote:
> OpenJDK project uses Cygwin to drive the OpenJDK build system under Windows. Recently, our GitHub
> Actions (GHA) Windows runs started to fail with make SEGV-ing:
> https://bugs.openjdk.java.net/browse/JDK-8276854
>
> This also reproduces locally for me, with the standard OpenJDK Windows build. All sightings we had
> are on Windows 10, but it is unclear if it is Windows 10 specific.
>
> The reproducer would be a bit hairy, because it requires MSVC 2019, JDK 17 binary, and some other
> dependencies to be installed for OpenJDK build. It goes like this:
>
> ------- 8< ------- ------- ------- ------- ------- ------- ------- -------
>
> <open Cygwin shell>
> $ git clone https://github.com/openjdk/jdk/ jdk
> $ cd jdk
> $ sh ./configure --with-boot-jdk=<jdk17-binary> --disable-warnings-as-errors
> $ make clean jdk
> ...
> Compiling 8 files for BUILD_TOOLS_LANGTOOLS
> Compiling 1 files for BUILD_TOOLS_HOTSPOT
> Compiling 12 properties into resource bundles for jdk.jdeps
> /usr/bin/bash: line 1: 1588 Segmentation fault (core dumped) /usr/bin/make -s -r -R -I
> /cygdrive/d/a/jdk17u/jdk17u/jdk/make/common
> SPEC=/cygdrive/d/a/jdk17u/jdk17u/jdk/build/windows-x64/spec.gmk MAKE_LOG_FLAGS="-s" -f
> ModuleWrapper.gmk -I /cygdrive/d/a/jdk17u/jdk17u/jdk/make/common/modules
> -I/cygdrive/d/a/jdk17u/jdk17u/jdk/make/modules/java.base MODULE=java.base MAKEFILE_PREFIX=Copy
> make[2]: *** [make/Main.gmk:157: java.base-copy] Error 139
> make[2]: *** Waiting for unfinished jobs....
> Compiling 7 properties into resource bundles for jdk.jshell
>
> ------- 8< ------- ------- ------- ------- ------- ------- ------- -------
Thanks for the report.
I could reproduce the problem and found that the cause is
the same with:
https://cygwin.com/pipermail/cygwin/2021-November/249913.html
I will submit the patch for these issues shortly.
--
Takashi Yano <takashi.yano@nifty.ne.jp>
next prev parent reply other threads:[~2021-11-16 8:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-15 16:47 Aleksey Shipilev
2021-11-15 17:32 ` Marco Atzeri
2021-11-16 8:11 ` Takashi Yano [this message]
2021-11-17 15:00 ` Aleksey Shipilev
2021-11-18 15:46 ` Jon Turney
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=20211116171113.8a284ca48adcefbb0f90fac7@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).