On Mon, 25 Nov 2019 08:15:46 -0500
Laura Abbott <labbott(a)redhat.com> wrote:
The process_configs.sh checks are designed to catch values changing
unexpecedtly the message
override: PSTORE_LZ4HC_COMPRESS_DEFAULT changes choice state
This indicates that some value set are now changed. This looks like
process_configs doing its job and not an actual error. It's also a
little hard to tell without seeing the full build log and what
changes you are actually making. I see two options:
Then this makes the kernel-local obsolete, because the point of having
a kernel-local file is to change config options from the default state.
I'm making extensive changes to the config file to customize it for my
system exclusively. File systems I don't use are gone. Graphics
devices I don't use are gone. Ditto audio devices. Ditto network
cards. etc.
When I use the custom config file with make oldconfig, there are no
complaints.
I notice that this is a warning rather than an actual error, even
though the configcheck is treating it as an error. Could configcheck
be changed to allow warnings to pass? Is there already a switch I can
pass to configcheck that does so?
1) Update the set of options you are setting to set all appropriate
dependencies
I tried this by setting various values in both kernel-local and in the
rpmbuild/SOURCES/kernel*.config file. No dice. Next kernel I build,
I'll do it in make menuconfig to see if it makes a difference.
2) Turn off the checking by building --without configchecks
It looks like this is what I'll have to do, though I don't like
bypassing consistency checks. Heh, my kernels have been building and
running fine for years without this, so maybe it's OK. :-)
Thanks.