From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: GNU make losing jobserver tokens in pipes
Date: Tue, 22 Mar 2022 11:52:03 -0600 [thread overview]
Message-ID: <638af4ef-e741-6ab1-6dfa-e64684e32f9e@SystematicSw.ab.ca> (raw)
In-Reply-To: <1a25a77b-b1de-edc0-974f-937e914d05fd@gmail.com>
On 2022-03-22 00:54, Noel Grandin wrote:
> On 2022/03/21 5:09 pm, Ken Brown wrote:
>> On 3/21/2022 10:28 AM, Magnus Ihse Bursie wrote:
>>> We have had a long-standing issue with make losing jobserver tokens.
>>> ("long-standing" here means for years, and years, at least since GNU
>>> make 4.0, up to and including the current latest version in Cygwin.)
> It was not that long ago that Linus Torvalds found a bug in the Linux
> kernel pipe implementation which caused GNU make to lose jobserver
> tokens, so possibly researching that bug may shed some light on the
> kinds of things that could be wrong with the Cygwin pipe code.
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=0ddad21d3e99c743a3aa473121dc5561679e26bb
>
> https://lkml.org/lkml/2019/12/18/1064
Perhaps add "in pipes" to subject to get that maintainer's attention?
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
next prev parent reply other threads:[~2022-03-22 17:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 14:28 GNU make losing jobserver tokens Magnus Ihse Bursie
2022-03-21 15:09 ` Ken Brown
2022-03-22 6:54 ` Noel Grandin
2022-03-22 17:52 ` Brian Inglis [this message]
2022-03-22 19:38 ` checking cyg version (was Re: GNU make losing jobserver tokens) L A Walsh
2022-03-22 21:58 ` Adam Dinwoodie
2022-03-22 23:06 ` Mark Geisert
2022-03-23 17:47 ` Samuel Lelièvre
2022-03-23 6:24 ` GNU make losing jobserver tokens Roumen Petrov
2022-04-01 8:45 ` Takashi Yano
2022-04-27 14:13 ` Takashi Yano
2022-04-28 13:42 ` Ken Brown
2022-04-28 14:09 ` Corinna Vinschen
2022-04-28 15:01 ` Takashi Yano
2022-04-28 15:32 ` Corinna Vinschen
2022-04-29 9:10 ` Takashi Yano
2022-04-30 21:51 ` Ken Brown
2022-05-01 0:51 ` Takashi Yano
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=638af4ef-e741-6ab1-6dfa-e64684e32f9e@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin@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).