Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.misc > #33170 > unrolled thread
| Started by | "Andrei Z." <no-email@invalid.invalid> |
|---|---|
| First post | 2021-09-07 08:46 +0300 |
| Last post | 2021-09-07 08:46 +0300 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.os.linux.misc
Enable '-Werror' by default for all kernel builds "Andrei Z." <no-email@invalid.invalid> - 2021-09-07 08:46 +0300
| From | "Andrei Z." <no-email@invalid.invalid> |
|---|---|
| Date | 2021-09-07 08:46 +0300 |
| Subject | Enable '-Werror' by default for all kernel builds |
| Message-ID | <sh6uca$1ff2$1@gioia.aioe.org> |
kernel/git/torvalds/linux.git https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3fe617ccafd6f5bb33c2391d6f4eeb41c1fd0151 <quote> Enable '-Werror' by default for all kernel builds ... but make it a config option so that broken environments can disable it when required. We really should always have a clean build, and will disable specific over-eager warnings as required, if we can't fix them. But while I fairly religiously enforce that in my own tree, it doesn't get enforced by various build robots that don't necessarily report warnings. So this just makes '-Werror' a default compiler flag, but allows people to disable it for their configuration if they have some particular issues. Occasionally, new compiler versions end up enabling new warnings, and it can take a while before we have them fixed (or the warnings disabled if that is what it takes), so the config option allows for that situation. Hopefully this will mean that I get fewer pull requests that have new warnings that were not noticed by various automation we have in place. Knock wood. Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> <unquote>
Back to top | Article view | comp.os.linux.misc
csiph-web