[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPOgqxFtH4Ezb1xVm3kOLBnOnQfpbs4==Kpefhaxz4JhOObqOA@mail.gmail.com>
Date: Mon, 16 Jan 2023 15:10:25 -0800
From: Amy Parker <apark0006@...dent.cerritos.edu>
To: Thomas Weißschuh <linux@...ssschuh.net>
Cc: linux-kernel@...r.kernel.org, linux-kbuild@...r.kernel.org
Subject: Re: Kernel builds now failing
On Mon, Jan 16, 2023 at 11:54 AM Thomas Weißschuh <linux@...ssschuh.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').
>
> 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.
Powered by blists - more mailing lists