From: Gary Thomas <gary@mlbassoc.com>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: Yocto Project <yocto@yoctoproject.org>
Subject: Re: Strange build warning
Date: Fri, 26 Aug 2011 09:52:36 -0600 [thread overview]
Message-ID: <4E57C144.2060901@mlbassoc.com> (raw)
In-Reply-To: <4E57BE73.8050809@windriver.com>
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
------------------------------------------------------------
next prev parent reply other threads:[~2011-08-26 15:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-26 15:32 Strange build warning Gary Thomas
2011-08-26 15:38 ` Gary Thomas
2011-08-26 15:40 ` Bruce Ashfield
2011-08-26 15:52 ` Gary Thomas [this message]
2011-08-26 16:12 ` Bruce Ashfield
2011-08-26 16:13 ` Bruce Ashfield
2011-08-26 15:45 ` Joshua Lock
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E57C144.2060901@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=bruce.ashfield@windriver.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.