From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Colin Walters <walters@verbum.org>,
Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: "poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: Re: Using linux-yocto_3.10 with dylan
Date: Wed, 23 Oct 2013 19:19:57 -0400 [thread overview]
Message-ID: <5268599D.4090801@windriver.com> (raw)
In-Reply-To: <1382570275.6691.87.camel@localhost>
On 13-10-23 07:17 PM, Colin Walters wrote:
> On Wed, 2013-10-23 at 19:06 -0400, Bruce Ashfield wrote:
>
>> It's the kernel tools. You need to bring back the matched tools -> the new 3.10
>> kernel tree, since they no longer use guilt to manage patches on branches, but
>> instead use pure git. The guilt tools can't detect that the patches are in fact
>> already applied to the tree, and try to push changes again, which lead to your
>> error.
>
> Ah hah! Yep, after a quick copy of kern-tools.bb from oe-core master
> and a "bitbake kern-tools-native", looks like "bitbake linux-yocto" is
> past do_patch and onto do_compile now. I should have posted a few hours
> earlier before I was knee deep in debugging prints and generated shell
> scripts...
:( sorry about that. The tools are always backwards compatible, but the
newest
kernel always needs the newest tools.
I have a solution to this, and can finally bring it into play in yocto
1.6, where the copy of the tools in the kernel tree is actively used,
which means a tree always carries the tools that it needs .. and no more
issues like you ran into.
Bruce
>
> Thank you!
>
>
>
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky
>
prev parent reply other threads:[~2013-10-23 23:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-23 22:40 Using linux-yocto_3.10 with dylan Colin Walters
2013-10-23 23:06 ` Bruce Ashfield
2013-10-23 23:17 ` Colin Walters
2013-10-23 23:19 ` Bruce Ashfield [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=5268599D.4090801@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=bruce.ashfield@gmail.com \
--cc=poky@yoctoproject.org \
--cc=walters@verbum.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.