public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: Heads up: Problems with parallel make
Date: Tue, 14 Feb 2023 22:23:46 +0100	[thread overview]
Message-ID: <fffda69e-e5ed-d428-f9fc-71d509b0c3c0@gmail.com> (raw)
In-Reply-To: <6c9c801e-7ec6-5093-afd7-8111fc4692a3@Shaw.ca>

On 14.02.2023 17:49, Brian Inglis via Cygwin-apps wrote:
> On 2023-02-13 17:38, Ken Brown via Cygwin-apps wrote:
>> On 2/13/2023 6:44 PM, Brian Inglis wrote:
>>> On 2023-02-13 16:05, 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.
>>>
>>> There is some glibc? compatibility issue also with this recommended 
>>> workaround.
>>
>> Could you elaborate?  I don't know what issue you're seeing.
> 
> There have been reports from various projects mentioning problems in 
> other packages ending up at make 4.4 and FIFOs solved by reverting to 
> pipes.
> 
> There is a make 4.4.1 release candidate 4.40.0.90 with patches that may 
> help to deal with this:
> 
>      https://alpha.gnu.org/gnu/make/make-4.4.0.90.tar.lz{,.sig}
> 
> https://sv.gnu.org/bugs/index.php?group=make&report_id=111&fix_release_id=110&set=custom
> 

test version built and on the way

please check



  reply	other threads:[~2023-02-14 21:23 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 [this message]
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

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=fffda69e-e5ed-d428-f9fc-71d509b0c3c0@gmail.com \
    --to=marco.atzeri@gmail.com \
    --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).