From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Darren Hart <darren.hart@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: kernel-tools failure for linux-yoctort_3.0.bb for poky/edison branch.
Date: Thu, 12 Jan 2012 16:27:00 -0500 [thread overview]
Message-ID: <4F0F5024.501@windriver.com> (raw)
In-Reply-To: <4F0F4801.10102@intel.com>
On 12-01-12 03:52 PM, Darren Hart wrote:
> On 01/12/2012 12:39 PM, Tom Zanussi wrote:
>> On Fri, 2011-12-16 at 19:03 -0800, Bruce Ashfield wrote:
>>> On 11-12-16 8:34 PM, Darren Hart wrote:
>>>> On 12/16/2011 05:22 PM, Bodke, Kishore K wrote:
>>>>>
>>>>> With the attached Darren's kern-tools-native_git.bb file, build was success.
>>>>> Thanks
>>>>> Kishore.
>>>>
>>>> See the patch I just sent:kern-tools: Include do_install() in bbappend
>>>> for what I believe to be the solution.
>>>>
>>>> I suppose the proper solution would be to version the kern-tools-native
>>>> recipe when major things like that change, but given the nature of this
>>>> layer, I think the above patch is adequate.
>>>
>>> That's not the solution to either problem (well, yes, it's a solution
>>> and there's nothing inherently wrong with it, it's just covering up
>>> the underlying issue) which is a layer dependency issue. In this case,
>>> meta-kernel-dev tracks the master branch of poky, not any other branch
>>> or version. And that is implicit, not explicit, hence why it got into
>>> this tangle.
>>>
>>> We could simply branch meta-kernel-dev and have an edison branch for
>>> it, not modify the appends to contain something that will just break
>>> again in the future.
>>>
>>> But meta-kernel-dev isn't officially used by much at the moment, so
>>> I'm not convinced that branching it is worth the trouble (but I can
>>> be convinced otherwise). I'd rather either just remove the kern-tools
>>> bbappend (I'm probably the only one on the planet that really needs
>>> it), or just trust people to know what they are up to with the
>>> meta-kernel-dev layer.
>>>
>>
>> Revisiting this - meta-kernel-dev is used in the documentation, and
>> Scott has now run up against this when testing and updating it. Since
>> the documentation does use edison, and the walk-throughs have the user
>> check out edison branches of both poky and the BSP layers, it would be
>> consistent to have the user also do the same for meta-kernel-dev.
>> Probably just an edison branch with the kern-tools bbappend removed
>> would work fine...
>>
>> Tom
>
> Works for me.
Seems ok. I can create a branch shortly, once I'm slightly out from
under my 3.2 tree creation rush.
Bruce
>
next prev parent reply other threads:[~2012-01-12 21:27 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-13 22:50 kernel-tools failure for linux-yoctort_3.0.bb for poky/edison branch Bodke, Kishore K
2011-12-13 23:05 ` Bruce Ashfield
2011-12-13 23:15 ` Darren Hart
2011-12-13 23:17 ` Bodke, Kishore K
2011-12-13 23:24 ` Bruce Ashfield
2011-12-13 23:26 ` Bodke, Kishore K
2011-12-14 5:13 ` Bruce Ashfield
2011-12-14 5:47 ` Darren Hart
2011-12-14 14:07 ` Bruce Ashfield
2011-12-16 19:27 ` Bodke, Kishore K
2011-12-16 19:29 ` Bruce Ashfield
2011-12-16 19:32 ` Darren Hart
2011-12-16 19:39 ` Bodke, Kishore K
2011-12-16 20:18 ` Darren Hart
2011-12-16 22:12 ` Bodke, Kishore K
2011-12-16 23:07 ` Darren Hart
2011-12-17 1:06 ` Bodke, Kishore K
2011-12-17 1:22 ` Bodke, Kishore K
2011-12-17 1:34 ` Darren Hart
2011-12-17 3:03 ` Bruce Ashfield
2011-12-17 3:17 ` Darren Hart
2011-12-19 22:11 ` Bodke, Kishore K
2012-01-12 20:39 ` Tom Zanussi
2012-01-12 20:52 ` Darren Hart
2012-01-12 21:27 ` Bruce Ashfield [this message]
2012-01-13 15:41 ` Bruce Ashfield
2012-01-13 15:45 ` Tom Zanussi
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=4F0F5024.501@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=darren.hart@intel.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.