[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK7LNAS8q9eDerwVRbPbqd+AKjNVkEKLOW+NAKaD4duP-gViqw@mail.gmail.com>
Date: Fri, 1 Dec 2023 00:42:18 +0900
From: Masahiro Yamada <masahiroy@...nel.org>
To: Sergey Senozhatsky <senozhatsky@...omium.org>
Cc: Patrick Georgi <pgeorgi@...gle.com>, linux-kbuild@...r.kernel.org,
linux-kernel@...r.kernel.org, Stefan Reinauer <reinauer@...gle.com>
Subject: Re: [PATCH] kconfig: WERROR unmet symbol dependency
On Wed, Nov 29, 2023 at 1:13 PM Sergey Senozhatsky
<senozhatsky@...omium.org> wrote:
>
> On (23/11/28 23:19), Masahiro Yamada wrote:
>
> [..]
>
> > KCONFIG_WERROR is meant to turn all warnings
> > to errors.
> > I do not see getenv("KCONFIG_WERROR")
> > sprinkled everywhere in Kconfig.
> > One more thing, you cannot directly exit(1)
> > from sym_calc_value().
>
> We do exit(1) for KCONFIG_WARN_UNKNOWN_SYMBOLS in conf_read().
>
> I can introduce two new helpers that will tell if confdata.c and symbol.c
> triggered any warnings and if KCONFIG_WERROR is set. And then different
> code paths can call them and handle exit gracefully, depending on the
> context (ncurses, menu, etc.).
>
> Something like this
I do not want to patch warnings one by one.
I will take some time to think about it.
--
Best Regards
Masahiro Yamada
Powered by blists - more mailing lists