From: Ken Brown <kbrown@cornell.edu>
To: cygwin-apps@cygwin.com
Subject: Re: Heads up: Problems with parallel make
Date: Mon, 13 Feb 2023 21:33:29 -0500 [thread overview]
Message-ID: <5e5e465b-9277-2115-71fd-48eff0f3bcab@cornell.edu> (raw)
In-Reply-To: <9c9fb865-5f11-67ec-81a5-9c1ee37b5ee1@cornell.edu>
On 2/13/2023 6:05 PM, Ken Brown via Cygwin-apps wrote:
> Several of my packages that used to build fine with parallel make now
> require 'make -j1'. Without this I either get strange errors or a hang.
>
> I can't find any pattern to explain when the problem occurs and when it
> doesn't, but it seems to be due to a change in make, starting with
> version 4.4. By default, make now uses a FIFO rather than a pipe in its
> jobserver implementation. You can override this with the make flag
>
> --jobserver-style=pipe
>
> In all cases where I've tried this, parallel make works again.
>
> It wouldn't surprise me if there's a bug in Cygwin's FIFO implementation
> that's responsible for this, but I haven't yet tried to track it down.
I've now reported this upstream:
https://lists.gnu.org/archive/html/bug-make/2023-02/msg00029.html
Ken
prev parent reply other threads:[~2023-02-14 2:33 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-13 23:05 Ken Brown
2023-02-13 23:44 ` Brian Inglis
2023-02-14 0:38 ` Ken Brown
2023-02-14 16:49 ` Brian Inglis
2023-02-14 21:23 ` Marco Atzeri
2023-02-15 18:09 ` Ken Brown
2023-02-16 7:47 ` Marco Atzeri
2023-02-16 16:49 ` Brian Inglis
2023-02-16 18:57 ` Marco Atzeri
2023-02-16 22:48 ` Brian Inglis
2023-02-17 2:21 ` Ken Brown
2023-02-19 22:50 ` Ken Brown
2023-02-20 17:00 ` Achim Gratz
2023-02-20 17:14 ` Ken Brown
2023-02-20 17:34 ` Marco Atzeri
2023-02-20 19:12 ` Marco Atzeri
2023-02-20 19:45 ` Ken Brown
2023-02-20 22:00 ` Ken Brown
2023-02-20 23:29 ` Ken Brown
2023-02-21 0:48 ` Ken Brown
2023-02-27 21:41 ` Brian Inglis
2023-02-27 22:45 ` Ken Brown
2023-03-02 6:32 ` Marco Atzeri
2023-02-20 17:35 ` Brian Inglis
2023-02-14 2:33 ` Ken Brown [this message]
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=5e5e465b-9277-2115-71fd-48eff0f3bcab@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin-apps@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).