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 09:00:26 -0700 [thread overview]
Message-ID: <5143459A.3060300@windriver.com> (raw)
In-Reply-To: <loom.20130315T160013-564@post.gmane.org>
On 13-03-15 08:04 AM, Volker Vogelhuber wrote:
> Hi,
>
>> 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.
> As mentioned in the first post, I checked out the danny branch.
>
> I used the following bitbake recipe for kernel compilation:
>
> inherit kernel
> require recipes-kernel/linux/linux-yocto.inc
>
> SECTION = "kernel"
> LICENSE = "GPLv2"
>
> LIC_FILES_CHKSUM = "file://COPYING;md5=d7810fab7487fb0aad327b76f1be7cd7"
>
>
> DESCRIPTION = "Linux kernel for the tao-boards"
> KERNEL_IMAGETYPE = "uImage"
> KERNEL_CC_append += "-mno-unaligned-access "
>
> COMPATIBLE_MACHINE = "(tao)"
>
> PV = "2.6.37"
>
> MACHINE_KERNEL_PR_append = "c+tn"
>
> SRC_URI = "file://linux-2.6.37-tn.tar.xz \
> file://defconfig \
> file://nonetwork.patch \
> file://rtc.patch \
> file://multitouch.patch"
>
> S = "${WORKDIR}/linux-2.6.37-tn"
>
> # Sadly perf is broken:
> do_compile_perf() {
> :
> }
>
> do_validate_branches() {
> :
> }
>
> do_install_perf() {
> :
> }
>
>
> After I removed the require recipes-kernel/linux/linux-yocto.inc
> line it worked. As you can see I have a .tar.xz file for the kernel source, so
> no git. But the git command within the linux-yocto.inc file
> realizes, that there is a git repository. But it's not one from the
> kernel, but from the poky repository the whole build environment is
> located in.
Hmmm. This is definitely supposed to error in the build process.
If you use linux-yocto-custom as a baseline recipe (from meta-skeleton),
you'll find the tgz that is unpacked by the build system is converted
to a git repository before the build starts, allow all the tool extensions
to work with configs that for one reason or another can't use a git
backed tree.
I just tested it here, and it worked, using the latest code in master.
Cheers,
Bruce
>
>
>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
prev parent reply other threads:[~2013-03-15 16:00 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
2013-03-15 15:04 ` Volker Vogelhuber
2013-03-15 16:00 ` 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=5143459A.3060300@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.