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, 27 Feb 2023 17:45:26 -0500	[thread overview]
Message-ID: <bee4ddd7-5f33-7f35-c824-c91ada50a8a6@cornell.edu> (raw)
In-Reply-To: <018c363b-ec06-37a6-ec52-09923381643e@Shaw.ca>

On 2/27/2023 4:41 PM, Brian Inglis via Cygwin-apps wrote:
> Looks like the 4.4.1 release disables FIFO on Hurd and Cygwin.
> Will be interesting to see if it is based on config test, for clues to 
> what it does not like, or just system?

In the case of HURD, it's because of failing tests in the test suite. 
In the case of Cygwin, it's because of the problem I reported, in which 
parallel make using a FIFO sometimes hangs when building TeX Live.

Anyone who wants to test this with their own builds can build make with

   CPPFLAGS=-DJOBSERVER_USE_FIFO=1

That will re-enable the use a FIFO for the jobserver.  One can then 
force make to use a pipe on a given project by using the make option

   --jobserver-style=pipe

I plan to do this myself, since I hope to debug the FIFO problem the 
next time I see it.  It's not easy to catch, because it doesn't happen 
with every build of TeX Live.  And when it does happen, the build has 
typically been going on for close to two hours before it hangs.

P.S. Marco, I don't know how much trouble you want to go to on this, but 
when you release make-4.4.1, you might also make a test release with 
CPPFLAGS set as above.  That would make it easier for adventurous people 
to try builds that use a FIFO.

  reply	other threads:[~2023-02-27 22:45 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 [this message]
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=bee4ddd7-5f33-7f35-c824-c91ada50a8a6@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).