All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Barker <paul.barker@commagility.com>
To: Denys Dmytriyenko <denys@ti.com>
Cc: meta-ti@yoctoproject.org
Subject: Re: linux-ti-staging: Error during parsing
Date: Tue, 20 Oct 2015 17:54:41 +0100	[thread overview]
Message-ID: <20151020175441.2adca0cc@centos-7> (raw)
In-Reply-To: <20151019222843.GL5620@edge>

On Mon, 19 Oct 2015 18:28:43 -0400
Denys Dmytriyenko <denys@ti.com> wrote:

> On Tue, Oct 13, 2015 at 08:00:42PM +0100, Paul Barker wrote:
> > Hi,
> > 
> > I'm trying to move from dylan forward to fido and ran into a parsing error with
> > the linux-ti-staging recipe (all versions in the tree). Here's a run through of
> > what I've done on a Centos 7 host with relevant output included. I'm using the
> > coresdk-2015.01 tag but there aren't any commits on the fido branch after this.
> > 
> > $ git clone http://arago-project.org/git/projects/oe-layersetup.git
> > 
> > $ cd oe-layersetup/
> > 
> > $ ./oe-layertool-setup.sh -f configs/coresdk/coresdk-2015.01-config.txt
> > 
> > $ cd build/
> > 
> > $ . conf/setenv
> > 
> > $ MACHINE=k2hk-evm bitbake core-image-minimal
> > NOTE: Started PRServer with DBfile: /home/COMMAGILITY/paul.barker/tmp/oe-layersetup/build/cache/prserv.sqlite3, IP: 127.0.0.1, PORT: 37851, PID: 8637
> > NOTE: Your conf/bblayers.conf has been automatically updated.
> > ERROR: ExpansionError during parsing /home/COMMAGILITY/paul.barker/tmp/oe-layersetup/sources/meta-ti/recipes-kernel/linux/linux-ti-staging_4.1.bb: Failure expanding variable SRCPV, expression was ${@bb.fetch2.get_srcrev(d)} which triggered exception Fet
> > chError: Fetcher failure: The SRCREV_FORMAT variable must be set when multiple SCMs are used.
> 
> Hi, Paul,
> 
> Quick question - what do you use for a toolchain? By default, coresdk config 
> you reference above expects pre-built Linaro toolchain (tested with 2015.05) 
> in your PATH. While it is supposed to give a meaningful error message when it 
> can't find the expected toolchain, sometimes I've seen it fail and give 
> absolutely cryptic one instead. Can you please grab the following tarball, 
> extract it and add it's bin/ dir to your PATH and try again? Thanks.
> 
> http://releases.linaro.org/15.05/components/toolchain/binaries/arm-linux-gnueabihf/gcc-linaro-4.9-2015.05-x86_64_arm-linux-gnueabihf.tar.xz
> 
> BTW, meta-arago allows you to control the toolchain with TOOLCHAIN_TYPE and 
> TOOLCHAIN_BRAND variables, defaulting to "external" and "linaro"...
> 

Denys,

I was using the 15.02-3 release of the Linaro toolchain. I upgraded to 15.05
and tried again but saw the same error.

Using 'bitbake -e' I've confirmed that TOOLCHAIN_TYPE="external" and
TOOLCHAIN_BRAND="linaro".

Thanks,

-- 
Paul Barker
CommAgility Ltd


      reply	other threads:[~2015-10-20 16:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20151013190042.GA8031@bang.betafive.co.uk>
2015-10-19 22:28 ` linux-ti-staging: Error during parsing Denys Dmytriyenko
2015-10-20 16:54   ` Paul Barker [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=20151020175441.2adca0cc@centos-7 \
    --to=paul.barker@commagility.com \
    --cc=denys@ti.com \
    --cc=meta-ti@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.