Jan 16, 2023 17:10:34 Amy Parker <apark0006@xxxxxxxxxxxxxxxxxxxx>: > 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'). 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 good. >> 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 package.