Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Tue, 17 Jan 2023 05:36:37 +0000
From:   Thomas =?utf-8?Q?Wei=C3=9Fschuh?= <thomas@t-8ch.de>
To:     Amy Parker <apark0006@student.cerritos.edu>
Cc:     Thomas =?utf-8?Q?Wei=C3=9Fschuh?= <linux@weissschuh.net>,
        linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org
Subject: Re: Kernel builds now failing
Message-ID: <20230117053637.viuu75chipgx42oi@t-8ch.de>
References: <CAPOgqxFva=tOuh1UitCSN38+28q3BNXKq19rEsVNPRzRqKqZ+g@mail.gmail.com>
 <20230116195357.2jq7q262tongxw52@t-8ch.de>
 <CAPOgqxFtH4Ezb1xVm3kOLBnOnQfpbs4==Kpefhaxz4JhOObqOA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CAPOgqxFtH4Ezb1xVm3kOLBnOnQfpbs4==Kpefhaxz4JhOObqOA@mail.gmail.com>
Precedence: bulk

On Mon, Jan 16, 2023 at 03:10:25PM -0800, Amy Parker wrote:
> On Mon, Jan 16, 2023 at 11:54 AM Thomas Wei?schuh <linux@weissschuh.net> wrote:
> > I expect this to be due to a change in make 4.4 that ignores SIGPIPEs [0].
> > So programs called from make will not receive a SIGPIPE when writing to
> > a closed pipe but instead an EPIPE write error.
> > `find` does not seem to handle this.
> 
> Thank you so much for the clarification! I've also seen reports of
> other tools not handling it (such as `yes').

I think this analysis was wrong. For me I got this error because on a
new ArchLinux installation the command "cpio" is not present, leading to
this cryptic error.
I sent a patch to make the error more obvious:
https://lore.kernel.org/all/20230117-kernel-kheaders-cpio-v1-1-058d3e1c8621@weissschuh.net/

Does it work for you after installing the package "cpio"?

It does not explain why it only stopped working for you recently,
though.

> > This behavior in make is new and I can't find a reasoning for it.
> > It also breaks other softwares builds.
> 
> Are you aware of active discussion regarding this on Savannah, or
> should I go and report the effects there?
> 
> > For now you can disable CONFIG_IKHEADERS and the build should work
> > again.
> 
> Alright, thanks. Did that, and re-ran my kernel build (allmodconfig).
> All works now.
> 
> > [0] make 4.4 was packaged for ArchLinux on 5th of January, so it would
> > fit the timeline.
> 
> Yep, running Make 4.4.