Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: New ARM error
Date: Wed, 28 Nov 2012 11:14:06 -0700	[thread overview]
Message-ID: <50B6546E.5070308@mlbassoc.com> (raw)

I build for an OMAP4 platform using
   DEFAULTTUNE = "cortexa9hf-neon"

This has been working fine, but after updating to the latest master, I'm getting this error

     Error, the PACKAGE_ARCHS variable does not contain TUNE_PKGARCH (cortexa9hf-neonhf-vfp-neon).
     PACKAGE_ARCHS = (all any noarch armv5hf-vfp armv5ehf-vfp armv6hf-vfp armv7ahf-vfp armv7ahf-vfp-neon cobra4430p82)

(I added the print of the expanded PACKAGE_ARCHS for clarity)

I bisected change this to this commit (Poky/Yocto tree):

commit c5b670e4c9f020ed951d5499a888c50b1d703b62
Author: Martin Jansa <Martin.Jansa@gmail.com>
Date:   Tue Oct 2 17:22:00 2012 +0000

     arm/arch-arm*: define ARMPKGARCH_tune-* for default tunes

     * tune-foo is not valid override, for it to work I had to add
       ARMPKGARCH = "${ARMPKGARCH_tune-${DEFAULTTUNE}}"
       but that doesn't work without value defined for every supported
       DEFAULTTUNE value, otherwise it's expanded like this
       TUNE_PKGARCH (${ARMPKGARCH_tune-armv5te}te).

     (From OE-Core rev: 31e4f2dee990ee7f5d7491b65565e71d7d580209)

     Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
     Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

Any ideas how I can fix this?

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------



             reply	other threads:[~2012-11-28 18:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-28 18:14 Gary Thomas [this message]
2012-11-28 21:42 ` New ARM error Martin Jansa
2012-11-29 12:02   ` Martin Jansa

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=50B6546E.5070308@mlbassoc.com \
    --to=gary@mlbassoc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox