From: Mihai Lindner <mihaix.lindner@linux.intel.com>
To: yocto@yoctoproject.org
Subject: Re: Cannot do atom-pc build with meta-cedartrail
Date: Thu, 27 Sep 2012 17:10:16 +0300 [thread overview]
Message-ID: <50645E48.7050208@linux.intel.com> (raw)
In-Reply-To: <CAJTo0LYvfkAbdngN6KA_wes62RgJYVAjYHKvyVv+unjQDmt2ew@mail.gmail.com>
On 2012-09-27 14:31, Burton, Ross wrote:
> Hi,
>
> If I add meta-intel and meta-cedartrail to my bblayers, when I try and
> do an atom-pc build (which I thought should still work, right?) I get
> the following error:
>
> NOTE: Error during finalise of
> /home/ross/Yocto/poky/meta/recipes-kernel/linux/linux-yocto_3.0.bb
> ERROR: ExpansionError during parsing
> /home/ross/Yocto/poky/meta/recipes-kernel/linux/linux-yocto_3.0.bb:
> Failure expanding variable SRCPV, expression was
> ${@bb.fetch2.get_srcrev(d)} which triggered exception FetchError:
> Fetcher failure for URL:
> 'git://git.yoctoproject.org/linux-yocto-3.0;protocol=git;bareclone=1;branch=yocto/standard/common-pc/atom-pc,meta,yocto/pvr;name=machine,meta,pvr'.
> Please set SRCREV to a valid value
>
> That's a bug, right?
>
> Ross
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>
That's a bug alright.
It seems the overall SRC_URI of linux-yocto is overwritten by meta-cedartrail layer, when included. Should be fixed by using SRC_URI_cedartrail instead.
--
Mihai Lindner
next prev parent reply other threads:[~2012-09-27 14:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-27 11:31 Cannot do atom-pc build with meta-cedartrail Burton, Ross
2012-09-27 14:10 ` Mihai Lindner [this message]
2012-09-27 17:07 ` Tom Zanussi
2012-09-29 20:50 ` Ross Burton
2012-10-02 15:00 ` Mihai Lindner
2012-10-02 16:02 ` Tom Zanussi
2012-10-03 16:15 ` Mihai Lindner
2012-09-28 22:36 ` Brian Lloyd
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=50645E48.7050208@linux.intel.com \
--to=mihaix.lindner@linux.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.