All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: meta-xilinx: ERROR: Failure expanding variable TUNE_PKGARCH ppc440
Date: Tue, 29 May 2012 13:36:23 -0500	[thread overview]
Message-ID: <4FC51727.6020205@windriver.com> (raw)
In-Reply-To: <E071AE73-05A7-4D16-9442-952E65ECA96C@gmail.com>

On 5/29/12 1:20 PM, Elvis Dowson wrote:
> Hi,
> I've added the meta-xilinx layer, and modified my build/conf/local.conf file as
> follows:
>
> # Set the target machine details
> MACHINE ?= "virtex5"
> # Set Xilinx Platform Studio hardware project path
> XILINX_BSP_PATH ?= "/project/xilinx-ml507"
> # Set target board
> XILINX_BOARD ?= "ml507"
>
> and when I try to build the meta-toolchain
>
> $ cd /tool/yocto/poky
> $ source oe-init-build-env build
> $ bitbake meta-toolchain
>
> I get the following errors:
>
> ERROR: Execution of event handler 'check_sanity_eventhandler' failed
> Traceback (most recent call last):
> File "/tool/yocto/poky/bitbake/lib/bb/utils.py", line 397, in
> better_eval(source=<code object <module> at 0x344b6b0, file "MACHINE_ARCH", line
> 1>, locals={'d': <bb.data_smart.DataSmart object at 0x1450050>}):
> def better_eval(source, locals):
>  > return eval(source, _context, locals)
> File "MACHINE_ARCH", line 1, in <module>
> File "/tool/yocto/poky/bitbake/lib/bb/data_smart.py", line 282, in
> DataSmart.getVar(var='TUNE_PKGARCH', expand=True, noweakdefault=False):
> if expand and value:
>  > return self.expand(value, var)
> return value
> File "/tool/yocto/poky/bitbake/lib/bb/data_smart.py", line 151, in
> DataSmart.expand(s='${@bb.utils.contains("TUNE_FEATURES", "ppc440", "ppc440",
> "${PPCPKGARCH}", d)}', varname='TUNE_PKGARCH'):
> def expand(self, s, varname = None):
>  > return self.expandWithRefs(s, varname).value
> File "/tool/yocto/poky/bitbake/lib/bb/data_smart.py", line 141, in
> DataSmart.expandWithRefs(s='${@bb.utils.contains("TUNE_FEATURES", "ppc440",
> "ppc440", "${PPCPKGARCH}", d)}', varname='TUNE_PKGARCH'):
> except Exception as exc:
>  > raise ExpansionError(varname, s, exc)
> ExpansionError: Failure expanding variable TUNE_PKGARCH, expression was
> ${@bb.utils.contains("TUNE_FEATURES", "ppc440", "ppc440", "${PPCPKGARCH}", d)}
> which triggered exception SyntaxError: EOL while scanning string literal
> (TUNE_PKGARCH, line 1)
>
> ERROR: Failure expanding variable TUNE_PKGARCH, expression was
> ${@bb.utils.contains("TUNE_FEATURES", "ppc440", "ppc440", "${PPCPKGARCH}", d)}
> which triggered exception SyntaxError: EOL while scanning string literal
> (TUNE_PKGARCH, line 1)
> ERROR: Command execution failed: Exited with 1
>
> Summary: There were 3 ERROR messages shown, returning a non-zero exit code.
>
> Has support for the PowerPC440 processor (present in the Virtex-5 FPGA) been
> removed from the newer gcc-versions?

The error above is an issue w/ the tune configuration.  In stock oe-core there 
is no 405/440 configuration.

You will need to create a new tune file, see 
meta/conf/machine/include/tune-ppc603e.inc as a reasonable example..

--Mark

> Best regards,
>
> Elvis Dowson
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core




  reply	other threads:[~2012-05-29 18:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-29 18:20 meta-xilinx: ERROR: Failure expanding variable TUNE_PKGARCH ppc440 Elvis Dowson
2012-05-29 18:36 ` Mark Hatle [this message]
2012-05-29 19:46   ` Elvis Dowson
2012-05-30  2:56     ` Khem Raj
2012-05-30 14:36       ` Adrian Alonso
2012-05-30 14:47         ` Elvis Dowson
2012-05-30 15:00           ` Khem Raj
2012-05-30 15:34             ` Elvis Dowson
2012-05-30 16:04               ` Khem Raj
2012-05-30 15:00           ` Mark Hatle

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=4FC51727.6020205@windriver.com \
    --to=mark.hatle@windriver.com \
    --cc=openembedded-core@lists.openembedded.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.