Re: [docs] [bitbake-devel] [PATCH 3/4] knotty: convert warnings to errors when -W is passed

["Antonin Godard" <antonin.godard@bootlin.com>]

Hi,

On Fri Oct 16, 2026 at 9:59 AM CEST, Michal Sieron via lists.openembedded.org wrote:
> Hi,
>
> two cents from my side. I think that warnings as errors would ideally work like normal -Werror in compilers.
>
> 1. Regarding name: -W doesn't indicate anything about errors. Only something
>    with warnings. I am not sure if having this short option is worth it.

I agree.

> 2. This might be controversial, but ability to do -Wno-error, would be great.
>    Problem is we don't have categorized/named warnings/errors. But I think
>    that it could support a syntax where we use file name (or partial match on
>    its path) and disable warnings-as-errors for that source file. Or this
>    might be even easier to implement: regex for warning message. It it
>    matches, it won't be treated as an error.

That sounds like an interesting idea - but maybe as a follow-up of this though?

> 3. Exit code only change won't force developers to immediately fix their code
>    as it's really easy to ignore in interactive terminals. Sure, later CI
>    would catch it, but I would prefer early fail if possible.

That's true - however, I checked again, and error messages originating from
bb.error (or bberror) do NOT stop the execution of bitbake. This is the role of
bb.fatal (or bbfatal). bb.error only affects the return code of bitbake, but
goes as far as possible - for example I was able to build an image recipe even
though one of its recipes emitted a bb.error.

So if we want warnings to act like errors, I think this is already what this
series does. If we want warnings/errors to act like bb.fatal, that's another
question.

Antonin