Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@linux.intel.com>
To: Poky <poky@yoctoproject.org>,
	openembedded-core@lists.openembedded.org,
	Kishore Bodke <kishore.k.bodke@intel.com>
Cc: Darren Hart <dvhart@linux.intel.com>
Subject: [PATCH 1/5] linux-libc-headers-yocto: Do not include linux-yocto
Date: Fri, 29 Jun 2012 12:54:31 -0700	[thread overview]
Message-ID: <4263ffefaa6f3b0069bc41c0f7578d36717edcfc.1340998763.git.dvhart@linux.intel.com> (raw)
In-Reply-To: <cover.1340998763.git.dvhart@linux.intel.com>

The only bit we seem to need from the linux-yocto include is the
SRCREV_FORMAT. If we define this explicitly, we can avoid including the
linux-yocto include.

This is desirable so that linux-yocto can require kernel and simplify
the PR update process of all the linux-yocto* recipes. Pulling in
kernel to the linux-libc-headers-yocto recipes causes build failures by
pulling in "update-modules-nativesdk".

Signed-off-by: Darren Hart <dvhart@linux.intel.com>
CC: Bruce Ashfield <bruce.ashfield@windriver.com>
CC: Tom Zanussi <tom.zanussi@intel.com>
---
 .../linux-libc-headers/linux-libc-headers-yocto_git.bb              |    3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/meta-yocto/recipes-kernel/linux-libc-headers/linux-libc-headers-yocto_git.bb b/meta-yocto/recipes-kernel/linux-libc-headers/linux-libc-headers-yocto_git.bb
index b4222f1..8ab4fb1 100644
--- a/meta-yocto/recipes-kernel/linux-libc-headers/linux-libc-headers-yocto_git.bb
+++ b/meta-yocto/recipes-kernel/linux-libc-headers/linux-libc-headers-yocto_git.bb
@@ -1,5 +1,4 @@
 require recipes-kernel/linux-libc-headers/linux-libc-headers.inc
-include recipes-kernel/linux/linux-yocto.inc
 
 B = "${S}"
 
@@ -13,6 +12,8 @@ SRCREV = "a1cdb60720c452c3965eaec3ec2cd10f06261cc5"
 PV = "3.4+git-${SRCPV}"
 PR = "r6"
 
+SRCREV_FORMAT ?= "meta_machine"
+
 SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.4.git;protocol=git;nocheckout=1;branch=${KBRANCH},meta;name=machine,meta"
 
 # force this to empty to prevent installation failures, we aren't
-- 
1.7.10.2




  reply	other threads:[~2012-06-29 20:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-29 19:54 [PATCH 0/5 V2] Enable building modules on target Darren Hart
2012-06-29 19:54 ` Darren Hart [this message]
2012-06-29 19:54 ` [PATCH 2/5] linux-yocto: Use INC_PR and move kernel require to linux-yocto.inc Darren Hart
2012-06-29 19:54 ` [PATCH 3/5] kernel: Add kernel headers to kernel-dev package Darren Hart
2012-06-29 20:01   ` Khem Raj
2012-06-29 20:09     ` Darren Hart
2012-06-29 19:54 ` [PATCH 4/5] tasl-core-sdk: Add kernel-dev to task-core-sdk RDEPENDS Darren Hart
2012-06-29 19:59   ` Darren Hart
2012-06-29 21:59   ` [poky] " Khem Raj
2012-06-29 23:01     ` Darren Hart
2012-06-29 23:23       ` Zhang, Jessica
2012-06-29 23:27         ` Darren Hart
2012-06-29 19:54 ` [PATCH 5/5] linux-yocto-custom: Remove linux-tools Darren Hart
2012-06-29 20:01   ` Bruce Ashfield
2012-06-29 20:03 ` [PATCH 0/5 V2] Enable building modules on target Bruce Ashfield

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=4263ffefaa6f3b0069bc41c0f7578d36717edcfc.1340998763.git.dvhart@linux.intel.com \
    --to=dvhart@linux.intel.com \
    --cc=kishore.k.bodke@intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox