All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Lock <josh@openedhand.com>
To: poky@yoctoproject.org
Subject: Re: linux recipe PV requirements
Date: Wed, 24 Nov 2010 11:42:07 +0000	[thread overview]
Message-ID: <1290598927.2799.14.camel@scimitar> (raw)
In-Reply-To: <4CEC613A.8020005@linux.intel.com>

On Tue, 2010-11-23 at 16:50 -0800, Darren Hart wrote:
> Are there restrictions on what the PV variable is set to?
> 
> I'd like to name the recipe I'm working on linux-linaro-2.6.35 and use 
> PR and the git AUTOREV to define the PV value. However, when I make the 
> following change in linux-linaro-2.6.35_git.bb:
> 
> - PV = "2.6.35"
> + PV = "${PR}+git${SRCREV}"

You need a kernel version in there, kernel.bbclass adds a depends to the
kernel of:

virtual/${TARGET_PREFIX}depmod-${@get_kernelmajorversion('${PV}')}

The get_kernelmajorversion() function in linux-kernel-base.bbclass is
failing to determine the kernel version and returning None which results
in the unbuildable dependency error you are seeing.

For further reference I'd point you at the PV's set by other git kernel
recipes:

joshual@scimitar:~/Projects/Yocto/poky/meta/recipes-kernel/linux
$ git grep PV\ =
linux-omap-zoomsync_2.6.32.bb:PV = "2.6.32.7-${OEV}"
linux-omap2_git.bb:PV = "2.6.26"
linux-omap2_git.bb:#PV = "2.6.26+2.6.27-rc1+${PR}+git${SRCREV}"
linux-omap3-pm_git.bb:PV = "2.6.31-rc7+pm+${PR}+git${SRCREV}"
linux-omap3_git.bb:PV = "2.6.27-rc6+${PR}+git${SRCREV}"
linux-yocto_git.bb:PV = "2.6.34+git${SRCPV}"

Cheers,
Joshua
-- 
Joshua Lock
        Intel Open Source Technology Centre



  reply	other threads:[~2010-11-24 11:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-24  0:50 linux recipe PV requirements Darren Hart
2010-11-24 11:42 ` Joshua Lock [this message]
2010-11-24 17:09   ` Darren Hart

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=1290598927.2799.14.camel@scimitar \
    --to=josh@openedhand.com \
    --cc=poky@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.