From: Brian Inglis <Brian.Inglis@Shaw.ca>
To: cygwin-apps@cygwin.com
Subject: Re: Heads up: Problems with parallel make
Date: Mon, 20 Feb 2023 10:35:37 -0700 [thread overview]
Message-ID: <728b7a29-827f-1aa2-5d9f-ee4f6a990176@Shaw.ca> (raw)
In-Reply-To: <39257fa6-df12-41d0-57fa-e26113a8efc6@cornell.edu>
On 2023-02-20 10:14, Ken Brown via Cygwin-apps wrote:
> On 2/20/2023 12:00 PM, Achim Gratz via Cygwin-apps wrote:
>> Ken Brown via Cygwin-apps writes:
>>> Thanks, Marco. As expected, that fixes the problem for my test case
>>> (building TeX Live). Obviously it would be better if the make
>>> developers would provide a configure option to use a pipe for the
>>> jobserver, but this is a good workaround if they don't.
>>
>> Does it actually do a parallel build? I've quickly tested a cmake based
>> project with it and it completely serializes the build. Reverting to
>> 4.4 resolves that problem.
>
> It does for my build of TeX Live. I just tried 'make -j13 check', and I saw
> many make processes and many sh processes running at once. [But I'm currently
> testing a self-built make 4.4.0.91.]
Definitely parallel jobs visible in top with make 4.4.0.90-1
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
La perfection est atteinte Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut
-- Antoine de Saint-Exupéry
next prev parent reply other threads:[~2023-02-20 17:35 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 [this message]
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=728b7a29-827f-1aa2-5d9f-ee4f6a990176@Shaw.ca \
--to=brian.inglis@shaw.ca \
--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).