Strange build warning

DISCUSSION Gary Thomas 3 participants 7 messages Aug 26, 2011

Share & tools

Gary Thomas

author

2011-08-26 15:32 UTC #0 lore raw

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?

Signature · 4 lines

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

Gary Thomas

author

2011-08-26 15:38 UTC #1 lore raw

Quoted 6 lines · Gary Thomas

Building 'bitbake core-image-sato' from scratch:
OE Build Configuration:
BB_VERSION = "1.13.3"
TARGET_ARCH = "i586"
TARGET_OS = "linux"
MACHINE = "qemux86"

Actually, MACHINE="atom_pc" (I grabbed the wrong screenshot)

Quoted 32 lines

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?

Signature · 4 lines

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

Bruce Ashfield

2011-08-26 15:40 UTC #2 lore raw

In reply to Gary Thomas

Quoted 32 lines · Gary Thomas

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

Quoted 5 lines

========================================================
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.

Bruce

Quoted 1 line

Gary Thomas

author

2011-08-26 15:52 UTC #3 lore raw

Quoted 40 lines · Bruce Ashfield

Quoted 39 lines · Gary Thomas
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.

Quoted 8 lines

Quoted 1 line
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?

Signature · 4 lines

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

Bruce Ashfield

2011-08-26 16:12 UTC #4 lore raw

Quoted 46 lines · Gary Thomas

Quoted 45 lines · Bruce Ashfield
Quoted 43 lines · Gary Thomas
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?

Quoted 8 lines

Quoted 6 lines
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?

Fixed:

http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=c03195482276d7c96d52f21562f8fa6a636f68a7

Bruce

Quoted 1 line

Bruce Ashfield

2011-08-26 16:13 UTC #5 lore raw

Quoted 57 lines · Bruce Ashfield

Quoted 56 lines · Gary Thomas
Quoted 54 lines · Bruce Ashfield
Quoted 41 lines · Gary Thomas
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
Quoted 5 lines
========================================================
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.

Quoted 5 lines

Quoted 1 line
So, is it fixed, or should I file a bug like Joshua recommended?
Fixed:
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=c03195482276d7c96d52f21562f8fa6a636f68a7

but I should add, if you are using meta-intel, and the meta SRCREV hasn't been bumped yet, you'd still see this.

Bruce

Quoted 10 lines

Bruce
Quoted 1 line
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

Joshua Lock

2011-08-26 15:45 UTC #6 lore raw

In reply to Gary Thomas

Quoted 33 lines · Gary Thomas

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.

Quoted 1 line

Is this important? If not, why scare me like this?

The generic infrastructure is important to maintain, if you're developing BSP's you likely want to know that your custom kernel config isn't producing the expected results.

In this instance the BSP is a Yocto maintained one and therefore this is a bug.

Regards,
Joshua

Signature · 3 lines

Joshua Lock
        Yocto Project "Johannes factotum"
        Intel Open Source Technology Centre