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 17:15:45 -0600 (CST)
From:   =?UTF-8?Q?Thomas_Wei=C3=9Fschuh_?= <thomas@t-8ch.de>
To:     Amy Parker <apark0006@student.cerritos.edu>
Cc:     =?UTF-8?Q?Thomas_Wei=C3=9Fschuh?= <linux@weissschuh.net>,
        linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org
Message-ID: <cad69928-92a2-472a-9ef4-99d3b74c0ab1@t-8ch.de>
In-Reply-To: <CAPOgqxFtH4Ezb1xVm3kOLBnOnQfpbs4==Kpefhaxz4JhOObqOA@mail.gmail.com>
References: <CAPOgqxFva=tOuh1UitCSN38+28q3BNXKq19rEsVNPRzRqKqZ+g@mail.gmail.com> <20230116195357.2jq7q262tongxw52@t-8ch.de> <CAPOgqxFtH4Ezb1xVm3kOLBnOnQfpbs4==Kpefhaxz4JhOObqOA@mail.gmail.com>
Subject: Re: Kernel builds now failing
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Precedence: bulk


Jan 16, 2023 17:10:34 Amy Parker <apark0006@student.cerritos.edu>:

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

Even bash os affected.

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

I got a pointer to the discussion after my first mail:
https://savannah.gnu.org/bugs/index.php?63307

It will be fixed in 4.4.1, testing the linked prerelease version would be g=
ood.

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

Nice.

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

Maybe it makes sense to ask for a backport for the fix for the ArchLinux pa=
ckage.