From: Hollis Blanchard <hollis_blanchard@mentor.com>
To: McClintock Matthew-B29882 <B29882@freescale.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: trouble using a local kernel repo
Date: Thu, 16 Feb 2012 13:33:03 -0800 [thread overview]
Message-ID: <4F3D760F.6020105@mentor.com> (raw)
In-Reply-To: <CAEsOVNfdiouZJ=qvN_GLBoLtJojHvdnXzVUoL674KN1LnNudYQ@mail.gmail.com>
On 02/16/2012 01:22 PM, McClintock Matthew-B29882 wrote:
> On Thu, Feb 16, 2012 at 8:16 PM, Hollis Blanchard
> <hollis_blanchard@mentor.com> wrote:
>> I'm trying to figure out how to use a cloned/modified copy of the
>> linux-yocto-3.0 git repository. Here's what I did:
>>
>> * cloned linux-yocto-3.0.git and committed to the meta branch
>> * specified my new repo:
>>
>> --- a/meta/recipes-kernel/linux/linux-yocto_3.0.bb
>> +++ b/meta/recipes-kernel/linux/linux-yocto_3.0.bb
>> @@ -18,12 +18,12 @@ SRCREV_machine_qemuppc ?=
>> "15fd748017f0849138ff4b47d73f6866fa26cfe8"
>> SRCREV_machine_qemux86 ?= "8f74a4339b3dc029fafff0ba7d88d6dc950d4b31"
>> SRCREV_machine_qemux86-64 ?= "610c5a62daeda033755b0b7bfcb3e2cad5c76f3f"
>> SRCREV_machine ?= "5df0b4c2538399aed543133b3855f809adf08ab8"
>> -SRCREV_meta ?= "b78a519841bd8b477cad599af8d38df6760445c1"
>> +SRCREV_meta ?= "7af8d6f8769335b79c1b76c8bded256b8f909c74"
>>
>> PR = "r3"
>> PV = "${LINUX_VERSION}+git${SRCPV}"
>>
>> -SRC_URI =
>> "git://git.yoctoproject.org/linux-yocto-3.0;protocol=git;nocheckout=1;branch=${KBRANCH},meta
>> +SRC_URI =
>> "git:///mnt/linux-yocto-3.0.git;protocol=file;nocheckout=1;branch=${KBRANCH},meta;name=machi
>>
>> COMPATIBLE_MACHINE = "(qemuarm|qemux86|qemuppc|qemumips|qemux86-64)"
>>
>> * bitbake -c clean virtual/kernel&& bitbake virtual/kernel
>>
>>
>> What I get is this:
>> ERROR: Function failed: do_validate_branches (see
>> /mnt/poky.git/build/tmp/work/beagleboard-poky-linux-gnueabi/linux-yocto-3.0.18+git2+7af8d6f8769335b79c1b76c8bded256b8f909c74_1+368e38c673ffac8b37fc2a2d4c1e4a1e6f8abf19-r3/temp/log.do_validate_branches.5342
>> for further information)
>>
>> There is no more information in that file. It contains only the exact
>> message I already got on the console ("ERROR: Function failed ...").
>>
>> What am I missing?
>> http://www.yoctoproject.org/docs/current/kernel-manual/kernel-manual.html
>> was not helpful.
> Not much help but you can look in:
>
> meta/classes/kernel-yocto.bbclass:do_validate_branches() {
>
> And try to figure out which step could return an error code to the shell.
Yeah, I've looked through there, but where should stdout (i.e. those
echo commands) be appearing?
Hollis Blanchard
Mentor Graphics, Embedded Systems Division
next prev parent reply other threads:[~2012-02-16 21:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-16 20:16 trouble using a local kernel repo Hollis Blanchard
2012-02-16 21:22 ` McClintock Matthew-B29882
2012-02-16 21:33 ` Hollis Blanchard [this message]
2012-02-16 21:43 ` McClintock Matthew-B29882
2012-02-16 22:06 ` Hollis Blanchard
2012-02-16 22:14 ` Bruce Ashfield
2012-02-16 22:11 ` Bruce Ashfield
2012-02-16 22:50 ` Hollis Blanchard
2012-02-16 23:02 ` Bruce Ashfield
2012-02-16 23:18 ` Hollis Blanchard
2012-02-16 23:25 ` Bruce Ashfield
2012-02-16 23:52 ` Hollis Blanchard
2012-02-17 0:13 ` Bruce Ashfield
2012-02-17 16:45 ` Hollis Blanchard
2012-02-17 19:56 ` 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=4F3D760F.6020105@mentor.com \
--to=hollis_blanchard@mentor.com \
--cc=B29882@freescale.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.