Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: "Andreas Müller" <schnitzeltony@googlemail.com>
Cc: meta-ti@yoctoproject.org,
	openembedded-devel@lists.openembedded.org,
	openembedded-core@lists.openembedded.org
Subject: Re: [meta-ti] massive fallout after updates / was (no subject)
Date: Thu, 21 Jun 2012 19:02:16 -0400	[thread overview]
Message-ID: <20120621230216.GD30753@denix.org> (raw)
In-Reply-To: <CALbNGRQCVUeZFX_xxVe=3ixZMm7MRt3WWB5VxemNs0Bi+qCHcQ@mail.gmail.com>

On Fri, Jun 22, 2012 at 12:11:46AM +0200, Andreas Müller wrote:
> On Thu, Jun 21, 2012 at 11:36 PM, Andreas Müller
> <schnitzeltony@googlemail.com> wrote:
> > after updating all my repos (angstrom+few extra layers) I get
> 
> The error seems to be caused by meta-ti. When removed, parsing works
> as expected. By re-including I get now:
> 
> ERROR: ExpansionError during parsing
> /home/Superandy/data/oe-core/sources/meta-ti/recipes-ti/gstreamer-ti/gstreamer-ti_svn.bb:
> Failure expanding variable FILESPATH, expression was
> ${@base_set_filespath([
> "/home/Superandy/data/oe-core/sources/meta-ti/recipes-ti/gstreamer-ti/gstreamer-ti-svnr962-r85+${MACHINE_KERNEL_PR}",

Could be caused by MACHINE_KERNEL_PR being undefined... What machine you are 
building for?

-- 
Denys


> "/home/Superandy/data/oe-core/sources/meta-ti/recipes-ti/gstreamer-ti/gstreamer-ti-svnr962",
> "/home/Superandy/data/oe-core/sources/meta-ti/recipes-ti/gstreamer-ti/gstreamer-ti",
> "/home/Superandy/data/oe-core/sources/meta-ti/recipes-ti/gstreamer-ti/gstreamer-ti-svnr962",
> "/home/Superandy/data/oe-core/sources/meta-ti/recipes-ti/gstreamer-ti/gstreamer-ti",
> "/home/Superandy/data/oe-core/sources/meta-ti/recipes-ti/gstreamer-ti/files",
> "/home/Superandy/data/oe-core/sources/meta-ti/recipes-ti/gstreamer-ti"
> ], d)} which triggered exception SyntaxError: EOL while scanning
> string literal (FILESPATH, line 1)
> ERROR: No recipes available for:
>   /home/Superandy/data/oe-core/sources/meta-intel/meta-sugarbay/recipes-kernel/linux/linux-yocto_3.2.bbappend
>   /home/Superandy/data/oe-core/sources/meta-intel/meta-crownbay/recipes-kernel/linux/linux-yocto_3.2.bbappend
>   /home/Superandy/data/oe-core/sources/meta-intel/meta-emenlow/recipes-kernel/linux/linux-yocto_3.2.bbappend
>   /home/Superandy/data/oe-core/sources/meta-intel/meta-fishriver/recipes-kernel/linux/linux-yocto_3.2.bbappend
>   /home/Superandy/data/oe-core/sources/meta-intel/meta-fri2/recipes-kernel/linux/linux-yocto_3.2.bbappend
>   /home/Superandy/data/oe-core/sources/meta-intel/meta-jasperforest/recipes-kernel/linux/linux-yocto_3.2.bbappend
>   ......
> 
> Andreas
> _______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
> 




  reply	other threads:[~2012-06-21 23:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-21 22:11 massive fallout after updates / was (no subject) Andreas Müller
2012-06-21 23:02 ` Denys Dmytriyenko [this message]
2012-06-21 23:34   ` [meta-ti] " Andreas Müller
2012-06-22  0:24     ` Denys Dmytriyenko

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=20120621230216.GD30753@denix.org \
    --to=denis@denix.org \
    --cc=meta-ti@yoctoproject.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=schnitzeltony@googlemail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox