From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Volker Vogelhuber <v.vogelhuber@digitalendoscopy.de>
Cc: yocto@yoctoproject.org
Subject: Re: building yocto image from git always switches branch
Date: Fri, 15 Mar 2013 07:34:15 -0700 [thread overview]
Message-ID: <51433167.2060009@windriver.com> (raw)
In-Reply-To: <loom.20130315T095848-21@post.gmane.org>
On 13-03-15 02:02 AM, Volker Vogelhuber wrote:
> Volker Vogelhuber <v.vogelhuber@...> writes:
>
>> When I change to the build directory and start building the image using
>> bitbake, there seems to be a git call somewhere in the recipes that
>> switches the branch of the poky git checkout back to master. Of course
>> that results in a total misbehaviour of the build process, as the
>> underlaying recipes changes during the build.
> It turned out, my own kernel recipe included
> recipes-kernel/linux/linux-yocto.inc
> which seems to require that the kernel is checked out from a git
> repository. After removing this include and only inherit from
> kernel.bbclass it worked as expected.
Interesting. Are you working out of yocto/oe-core master ? The linux
yocto kernel support should always fail if the kernel source dir
isn't a git repo (or convert it into one) and not impact the main
yocto/oe-core tree.
Cheers,
Bruce
>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
next prev parent reply other threads:[~2013-03-15 14:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 16:34 building yocto image from git always switches branch Volker Vogelhuber
2013-03-15 9:02 ` Volker Vogelhuber
2013-03-15 14:34 ` Bruce Ashfield [this message]
2013-03-15 15:04 ` Volker Vogelhuber
2013-03-15 16:00 ` 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=51433167.2060009@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=v.vogelhuber@digitalendoscopy.de \
--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.