From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Subject: Re: Regression in Cygwin 3.2.0
Date: Sat, 17 Apr 2021 21:37:14 +0900 [thread overview]
Message-ID: <20210417213714.2a3dad50885c85f4faf4e1b6@nifty.ne.jp> (raw)
In-Reply-To: <000b01d732a9$c15bf510$4413df30$@cl.cam.ac.uk>
On Fri, 16 Apr 2021 11:17:50 +0100
David Allsopp wrote:
> I'm unable to build OCaml using the mingw-w64 compilers with Cygwin 3.2.0.
> Windows 10.0.19042.928 (and tried on three different machines so far)
>
> Repro:
>
> - Fresh Cygwin64 installation with make, libiconv, mingw64-x86_64-gcc-core
> and git added; fire up mintty
> - git clone --depth 1 --recursive https://github.com/ocaml/ocaml
> - cd ocaml && ./configure --host=x86_64-w64-mingw32 && make -j8 flexdll &&
> make -j8 world.opt
>
> This is consistently hanging with Cygwin 3.2.0 and seems possibly to have
> something to do with linking (the creation of runtime/ocamlrun.exe and
> stdlib/camlheader, which is also an executable, seem to be part of the
> problem).
>
> It can be immediately fixed by downgrading to Cygwin 3.1.7, cleaning the
> tree and repeating the build.
>
> I'm of course very happy to try to reduce this to a smaller repro case, but
> is there an obvious culprit in Cygwin 3.2.0 to check before I do?
Thanks for the report. I looked into this problem and found
that the caused is the combination of some race issues for
non-cygwin processes in pty and console code.
I will submit the patches fixing this issue.
--
Takashi Yano <takashi.yano@nifty.ne.jp>
next prev parent reply other threads:[~2021-04-17 12:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-16 10:17 David Allsopp
2021-04-16 12:05 ` Thomas Wolff
2021-04-16 14:07 ` David Allsopp
2021-04-16 14:44 ` Thomas Wolff
2021-04-16 17:26 ` David Allsopp
2021-04-17 12:37 ` Takashi Yano [this message]
2021-04-18 10:58 ` David Allsopp
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=20210417213714.2a3dad50885c85f4faf4e1b6@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).