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:   Mon, 16 Jan 2023 19:53:57 +0000
From:   Thomas =?utf-8?Q?Wei=C3=9Fschuh?= <linux@weissschuh.net>
To:     Amy Parker <apark0006@student.cerritos.edu>
Cc:     linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org
Subject: Re: Kernel builds now failing
Message-ID: <20230116195357.2jq7q262tongxw52@t-8ch.de>
References: <CAPOgqxFva=tOuh1UitCSN38+28q3BNXKq19rEsVNPRzRqKqZ+g@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAPOgqxFva=tOuh1UitCSN38+28q3BNXKq19rEsVNPRzRqKqZ+g@mail.gmail.com>
Precedence: bulk

Hi Amy,

On Mon, Jan 16, 2023 at 11:24:19AM -0800, Amy Parker wrote:
> As of recent, my kernel builds have started failing. The error is consistently:
> 
> find: 'standard output': Broken pipe
> find: write error
> make[2]: *** [kernel/Makefile:157: kernel/kheaders_data.tar.xz] Error 127
> make[1]: *** [scripts/Makefile.build:504: kernel] Error 2
> 
> This fails on the default Arch configuration (6.1.5-arch2-1, defaults
> for all new features) as well as with allmodconfig.
> 
> Everything was building fine before - this may be a regression, or
> just may be a problem with something in my toolchain updating and
> causing it to break. In that case, any assistance with getting my
> toolchains back to being able to compile would be appreciated.

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.

This behavior in make is new and I can't find a reasoning for it.
It also breaks other softwares builds.

For now you can disable CONFIG_IKHEADERS and the build should work
again.

Thomas

[0] make 4.4 was packaged for ArchLinux on 5th of January, so it would
fit the timeline.