Re: Kernel builds now failing

[Thomas Weißschuh]

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@xxxxxxxxxxxxxx> 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@xxxxxxxxxxxxxx/

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.