public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: cygwin-apps@cygwin.com
Subject: Re: Heads up: Problems with parallel make
Date: Mon, 20 Feb 2023 18:29:59 -0500	[thread overview]
Message-ID: <eabdd8e7-fc18-90fb-7a75-d2bc2f5fd6e0@cornell.edu> (raw)
In-Reply-To: <8091faf0-36f7-7432-5eb8-020c31d347bb@cornell.edu>

On 2/20/2023 5:00 PM, Ken Brown via Cygwin-apps wrote:
> On 2/20/2023 2:12 PM, Marco Atzeri via Cygwin-apps wrote:
>> uploaded as test 4.4.0.91-1
>>
>>
>> following message is still present while missing in 4.4-1
>>
>>> make[1]: warning: jobserver unavailable: using -j1.  Add '+' to 
>>> parent make rule.
>>>
>>
>> and I do not see clear evidence of parallelism like in 4.4-1
> 
> I doubt if this is related to the pipe vs. fifo issue, but maybe you 
> should test 4.4.0.90-1 to be sure.
> 
> Do you have a simple way to reproduce the problem?  For example, does it 
> happen if you just make a toy cmake project?

Ignore what I said about 'make -j13 check' working right in the TeX Live 
build.  I just retried it and saw the "jobserver unavailable" message. 
When I saw several makes running at once, I think it was because of 
recursion, not parallelism.  So there's a real problem that can be 
reproduced without cmake.

Ken

  reply	other threads:[~2023-02-20 23:30 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 [this message]
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=eabdd8e7-fc18-90fb-7a75-d2bc2f5fd6e0@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).