On Fri, Oct 8, 2021 at 11:52 AM <mrkozmic@...> wrote:

I have defined LINUX_VERSION_EXTENSION in my kernel recipe.

I have no CONFIG_LOCALVERSION or CONFIG_LOCALVERSION_AUTO defined in my defconfig

After i run bitbake -c kernel_configme <my kernel recipe> I can see in my .config file:

CONFIG_LOCALVERSION=""
# CONFIG_LOCALVERSION_AUTO is not set

and at the very end:

CONFIG_LOCALVERSION="<my extention>"
So far so good.

Then I execute bitbake -c configure <my kernel recipe>
and the .config file is changed. Now there is:
CONFIG_LOCALVERSION=""
CONFIG_LOCALVERSION_AUTO=y
and there is no trace of CONFIG_LOCALVERSION="<my extention>"

Assuming what you are using as a kernel recipe is linux-yocto based,
the code that is adding the CONFIG_LOCALVERSION is a task that runs
after do_configure. So just running -c configure, it shouldn't be in
the .config (and the default kernel configure task, will copy your
defconfig -> .config, and then lets the kernel process it, so you will
have symbols in the .config that are not in your defconfig
explicitly).

If you can make your recipe available, I can probably offer more
specific comments.

Bruce

Yocto: dunfell
Kernel 5.4.70

--
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II