[yocto] Strange build warning

[Gary Thomas]

On 2011-08-26 09:40, Bruce Ashfield wrote:
> On 11-08-26 11:32 AM, Gary Thomas wrote:
>> Building 'bitbake core-image-sato' from scratch:
>> OE Build Configuration:
>> BB_VERSION = "1.13.3"
>> TARGET_ARCH = "i586"
>> TARGET_OS = "linux"
>> MACHINE = "qemux86"
>> DISTRO = "poky"
>> DISTRO_VERSION = "1.0+snapshot-20110826"
>> TUNE_FEATURES = "m32 i586"
>> TARGET_FPU = ""
>> meta
>> meta-yocto = "master:6c2b7beac3cd23ed44bd3e195c6360a0932876bf"
>>
>> I saw this warning:
>> =======================================================
>> This BSP sets 1 invalid/obsolete kernel options.
>> These config options are not offered anywhere within this kernel.
>> The full list can be found in your workspace at:
>> /local/pc_poky/tmp/work/atom_pc-poky-linux/linux-yocto-3.0.3+git1+5b535279e61197cb194bb2dfceb8b7a04128387c_1+ead7d8334e4c075906d029789333f43e54f6257a-r1/linux/meta/cfg/yocto/standard/common-pc/atom-pc/invalid.cfg
>>
>>
>>
>> This BSP sets 11 kernel options that are possibly non-hardware related.
>> The full list can be found in your workspace at:
>> /local/pc_poky/tmp/work/atom_pc-poky-linux/linux-yocto-3.0.3+git1+5b535279e61197cb194bb2dfceb8b7a04128387c_1+ead7d8334e4c075906d029789333f43e54f6257a-r1/linux/meta/cfg/yocto/standard/common-pc/atom-pc/specified_non_hdw.cfg
>>
>>
>>
>> WARNING: There were 88 hardware options requested that do not
>> have a corresponding value present in the final ".config" file.
>> This probably means you aren't getting the config you wanted.
>> The full list can be found in your workspace at:
>> /local/pc_poky/tmp/work/atom_pc-poky-linux/linux-yocto-3.0.3+git1+5b535279e61197cb194bb2dfceb8b7a04128387c_1+ead7d8334e4c075906d029789333f43e54f6257a-r1/linux/meta/cfg/yocto/standard/common-pc/atom-pc/mismatch.cfg
>>
>>
>> ========================================================
>> along with a note that the build was pausing for a few seconds so I
>> would notice the error/warning.
>>
>> Is this important? If not, why scare me like this?
>
> It was a temporary warning when I forgot to bump the internal
> version in the kernel tree, to match the external recipe one.
>
> It's just telling you that it couldn't audit to be sure that
> any configs you asked for .. made it to the final build. But
> in this case, I can assure you that they did.

So, is it fixed, or should I file a bug like Joshua recommended?

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------