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: Thu, 16 Feb 2023 21:21:45 -0500	[thread overview]
Message-ID: <c346ce58-4497-dfcd-1b02-9b47bd5a5e07@cornell.edu> (raw)
In-Reply-To: <4891b215-8bbc-431a-db83-f2c980538ffd@gmail.com>

On 2/16/2023 2:47 AM, Marco Atzeri via Cygwin-apps wrote:
> On 15.02.2023 19:09, Ken Brown via Cygwin-apps wrote:
>> On 2/14/2023 4:23 PM, Marco Atzeri via Cygwin-apps wrote:
>>> On 14.02.2023 17:49, Brian Inglis via Cygwin-apps wrote:
>>>> 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
>>
>> The problems I reported with make 4.4 still exist in 4.4.0.90.
>>
>> Until someone can figure out why this happens, you might want to 
>> consider building make so that it doesn't default to using a FIFO for 
>> its jobserver.  I suggested to the make developers that they provide a 
>> configure option for this purpose.  If they don't do this, I think you 
>> could accomplish the same thing by configuring make with 
>> ac_cv_func_mkfifo=no.
>>
>> Ken
> 
> version 2 uploaded.

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.

Ken

  parent reply	other threads:[~2023-02-17  2:21 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 [this message]
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=c346ce58-4497-dfcd-1b02-9b47bd5a5e07@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).