linux-kernel - RE: I disabled more compiler warnings..

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 11 May 2020 07:43:32 +0000
From:   David Laight <David.Laight@...LAB.COM>
To:     'Linus Torvalds' <torvalds@...ux-foundation.org>,
        Arnd Bergmann <arnd@...db.de>,
        Masahiro Yamada <yamada.masahiro@...ionext.com>
CC:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: RE: I disabled more compiler warnings..

From: Linus Torvalds
> Sent: 10 May 2020 20:33
...
> And as part of that, there were a lot of new warnings in the kernel build.
> 
> I let them go for a while, in the belief that I could deal with it,
> but then yesterday I did a pull and didn't initially even notice that
> the end result didn't compile for me, because the build error was
> hidden by the hundreds of lines of warnings ...

One problem is that gmake is very bad at stopping parallel
makes when one command fails.
So the kernel build carries on firing off new compilations
even after one has failed.

I've not looked inside gmake, but I fixed nmake so that it
properly used a single job token pipe for the entire (NetBSD)
build and then flushed and refilled it with 'abort' tokens
when any command failed.
That made the build stop almost immediately.

	David

-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)