From: Darren Hart <dvhart@linux.intel.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: Poky <poky@yoctoproject.org>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [poky] [PATCH 4/5] tasl-core-sdk: Add kernel-dev to task-core-sdk RDEPENDS
Date: Fri, 29 Jun 2012 16:01:31 -0700 [thread overview]
Message-ID: <4FEE33CB.3010609@linux.intel.com> (raw)
In-Reply-To: <CAMKF1sqrg5O7A1Tt=XjTzc0PfV5ZKcETe1tJfHOP460NNmpojw@mail.gmail.com>
On 06/29/2012 02:59 PM, Khem Raj wrote:
>> ALLOW_EMPTY = "1"
>> #PACKAGEFUNCS =+ 'generate_sdk_pkgs'
>> @@ -46,7 +46,8 @@ RDEPENDS_task-core-sdk = "\
>> distcc \
>> ldd \
>> file \
>> - tcl"
>> + tcl \
>> + kernel-dev"
>
> Doesn't this.make sdk to be machine specific now
It does indeed as the kernel-dev contains the system map, config, and
possibly even modified headers dependingon the KBRANCH.
Is task-core-sdk intended to be only architecture specific?
If so, I can just add kernel-dev to the -sdk image recipes directly
rather than modifying task-core-sdk.
Jessica, any opinion here?
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
WARNING: multiple messages have this Message-ID (diff)
From: Darren Hart <dvhart@linux.intel.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: Poky <poky@yoctoproject.org>,
Kishore Bodke <kishore.k.bodke@intel.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 4/5] tasl-core-sdk: Add kernel-dev to task-core-sdk RDEPENDS
Date: Fri, 29 Jun 2012 16:01:31 -0700 [thread overview]
Message-ID: <4FEE33CB.3010609@linux.intel.com> (raw)
In-Reply-To: <CAMKF1sqrg5O7A1Tt=XjTzc0PfV5ZKcETe1tJfHOP460NNmpojw@mail.gmail.com>
On 06/29/2012 02:59 PM, Khem Raj wrote:
>> ALLOW_EMPTY = "1"
>> #PACKAGEFUNCS =+ 'generate_sdk_pkgs'
>> @@ -46,7 +46,8 @@ RDEPENDS_task-core-sdk = "\
>> distcc \
>> ldd \
>> file \
>> - tcl"
>> + tcl \
>> + kernel-dev"
>
> Doesn't this.make sdk to be machine specific now
It does indeed as the kernel-dev contains the system map, config, and
possibly even modified headers dependingon the KBRANCH.
Is task-core-sdk intended to be only architecture specific?
If so, I can just add kernel-dev to the -sdk image recipes directly
rather than modifying task-core-sdk.
Jessica, any opinion here?
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2012-06-29 23:14 UTC|newest]
Thread overview: 24+ 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 ` [PATCH 1/5] linux-libc-headers-yocto: Do not include linux-yocto Darren Hart
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:01 ` Khem Raj
2012-06-29 20:09 ` Darren Hart
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 19:59 ` Darren Hart
2012-06-29 21:59 ` [poky] " Khem Raj
2012-06-29 21:59 ` Khem Raj
2012-06-29 23:01 ` Darren Hart [this message]
2012-06-29 23:01 ` Darren Hart
2012-06-29 23:23 ` [poky] " Zhang, Jessica
2012-06-29 23:23 ` Zhang, Jessica
2012-06-29 23:27 ` [poky] " Darren Hart
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:01 ` Bruce Ashfield
2012-06-29 20:03 ` [PATCH 0/5 V2] Enable building modules on target Bruce Ashfield
2012-06-29 20:03 ` 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=4FEE33CB.3010609@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=poky@yoctoproject.org \
--cc=raj.khem@gmail.com \
/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.