From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Elvis Dowson <elvis.dowson@gmail.com>
Cc: yocto@yoctoproject.org,
meta-xilinx Mailing List <meta-xilinx@yoctoproject.org>
Subject: Re: [meta-xilinx] PREFERRED_VERSION_linux-libc-headers = "3.6" getting ignored
Date: Fri, 19 Apr 2013 09:25:24 +0100 [thread overview]
Message-ID: <1392229.rlL64ybf7G@helios> (raw)
In-Reply-To: <FB1FE6F3-40EC-4711-95D0-5633B0103297@gmail.com>
On Friday 19 April 2013 11:44:49 Elvis Dowson wrote:
> In my zynq-7-default-versions.inc file, I have the following
> definitions for preferred versions
>
> PREFERRED_VERSION_virtual/kernel ?= "3.6"
> PREFERRED_VERSION_linux-libc-headers = "3.6"
> PREFERRED_VERSION_u-boot = "2012.10"
>
> However, when I build core-image-minimal,
> PREFERRED_VERSION_linux-libc-headers = "3.6" gets ignored and it goes ahead
> and builds linux-libc-headers_3.8.bb
>
> Is it only effective if specified in the local.conf file?
No, it should be effective anywhere - unless it's being overridden later on. In
recent versions of bitbake, the -e option will show for each variable how the
final value got set, you should be able to see where it is being overridden
from there. Alternatively with older versions you should just be able to "git
grep" for the value in each of the layers you have enabled in order to find
where it is being set.
Are you sure you really need your own version of linux-libc-headers? Most of
the time it is not necessary for the version to match that of the kernel you
are using.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
prev parent reply other threads:[~2013-04-19 8:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-19 7:44 [meta-xilinx] PREFERRED_VERSION_linux-libc-headers = "3.6" getting ignored Elvis Dowson
2013-04-19 8:25 ` Paul Eggleton [this message]
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=1392229.rlL64ybf7G@helios \
--to=paul.eggleton@linux.intel.com \
--cc=elvis.dowson@gmail.com \
--cc=meta-xilinx@yoctoproject.org \
--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.