From: Kees Cook <kees@kernel.org>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: Lorenzo Stoakes <ljs@kernel.org>, Nicolas Schier <nsc@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Manuel Ebner <manuelebnerli@mailbox.org>,
Nathan Chancellor <nathan@kernel.org>,
linux-kbuild@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, workflows@vger.kernel.org,
Mark Brown <broonie@kernel.org>,
linux-next@vger.kernel.org
Subject: Re: [BUG] Build failure in next-20261007 and next-20261008
Date: Fri, 9 Oct 2026 19:23:29 -0700 [thread overview]
Message-ID: <202610091922.19792FDA8@keescook> (raw)
In-Reply-To: <51aa9736-6e78-40db-9d4f-95dc7142e222@paulmck-laptop>
On Fri, Oct 09, 2026 at 08:57:02AM -0700, Paul E. McKenney wrote:
> On Thu, Oct 08, 2026 at 10:11:14PM -0700, Kees Cook wrote:
> > On Thu, Oct 08, 2026 at 05:56:21PM -0700, Paul E. McKenney wrote:
> > > Building a kernel on CentOS Stream 9 from next-20261007 and next-20261008
> > > (and maybe others?) on an x86 or arm64 system results in a strange
> > > build failure featuring:
> > >
> > > WARNING: Unable to reopen jobserver read-side pipe: FileNotFoundError(2, 'No such file or directory')
> >
> > What are your make and python versions? (Oh, the answer is going to be
> > "CentOS-patched make 4.3")
>
> I get "GNU Make 4.3", so maybe I need to patch or upgrade or something?
>
> And "Python 3.12.15+meta", so maybe I need to talk to people here. ;-)
I meant, it looks like CentOS has a patched version of "make". But I
think that just changes the nature of the bug; it's still a bug that
needs to be fixed even with unpatched "make".
--
Kees Cook
next prev parent reply other threads:[~2026-10-10 2:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 0:56 Paul E. McKenney
2026-10-09 5:11 ` Kees Cook
2026-10-09 15:57 ` Paul E. McKenney
2026-10-10 2:23 ` Kees Cook [this message]
2026-10-10 4:28 ` Paul E. McKenney
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=202610091922.19792FDA8@keescook \
--to=kees@kernel.org \
--cc=broonie@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=ljs@kernel.org \
--cc=manuelebnerli@mailbox.org \
--cc=mchehab@kernel.org \
--cc=nathan@kernel.org \
--cc=nsc@kernel.org \
--cc=paulmck@kernel.org \
--cc=workflows@vger.kernel.org \
/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
all inboxes | Powered by JetHome®