From: Patrick Ohly <patrick.ohly@intel.com>
To: OpenEmbedded <openembedded-core@lists.openembedded.org>
Subject: multiconfig + siteinfo.bbclass
Date: Wed, 14 Dec 2016 16:37:43 +0100 [thread overview]
Message-ID: <1481729863.1544.33.camel@intel.com> (raw)
Hello!
While trying out a multiconfig with two configurations (one for MACHINE
= intel-corei7-64, one for quark) in custom Ostro derivative I got an
error while parsing recipes:
ERROR: /work/iot-ref-kit/openembedded-core/../meta-openembedded/meta-python/recipes-devtools/python/python-m2crypto_0.23.0.bb: Unable to determine endianness for architecture 'INVALID'
That error comes from OE-core's meta/classes/siteinfo.bbclass;
python () {
sitedata = set(siteinfo_data(d))
if "endian-little" in sitedata:
d.setVar("SITEINFO_ENDIANNESS", "le")
elif "endian-big" in sitedata:
d.setVar("SITEINFO_ENDIANNESS", "be")
else:
bb.error("Unable to determine endianness for architecture '%s'" %
d.getVar("HOST_ARCH", True))
bb.fatal("Please add your architecture to siteinfo.bbclass")
HOST_ARCH is set to "x86_64" when not using BBMULTICONFIG in local.conf.
It's not specific to that recipe, everything using siteinfo.bbclass
seems to be affected. OE-core is d62f18c3 and bitbake is b65a81933 -
both fairly recent, but not quite master. I don't see any relevant
changes since then.
However, I can't reproduce this with just Poky :-/ Any suggestions?
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
next reply other threads:[~2016-12-14 15:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-14 15:37 Patrick Ohly [this message]
2016-12-14 18:13 ` multiconfig + siteinfo.bbclass Patrick Ohly
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=1481729863.1544.33.camel@intel.com \
--to=patrick.ohly@intel.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