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;
MIME-Version: 1.0
References: <CAPOgqxFva=tOuh1UitCSN38+28q3BNXKq19rEsVNPRzRqKqZ+g@mail.gmail.com>
 <20230116195357.2jq7q262tongxw52@t-8ch.de>
In-Reply-To: <20230116195357.2jq7q262tongxw52@t-8ch.de>
From:   Amy Parker <apark0006@student.cerritos.edu>
Date:   Mon, 16 Jan 2023 15:10:25 -0800
Message-ID: <CAPOgqxFtH4Ezb1xVm3kOLBnOnQfpbs4==Kpefhaxz4JhOObqOA@mail.gmail.com>
Subject: Re: Kernel builds now failing
To:     =?UTF-8?Q?Thomas_Wei=C3=9Fschuh?= <linux@weissschuh.net>
Cc:     linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

On Mon, Jan 16, 2023 at 11:54 AM Thomas Wei=C3=9Fschuh <linux@weissschuh.ne=
t> 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').

>
> 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.