multiconfig + siteinfo.bbclass

multiconfig + siteinfo.bbclass

[Patrick Ohly]

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.

Re: multiconfig + siteinfo.bbclass

[Patrick Ohly]

On Wed, 2016-12-14 at 16:37 +0100, Patrick Ohly wrote:
> 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:
> 
[...]
> 
> However, I can't reproduce this with just Poky :-/ Any suggestions?

Turned out to be a user error combined with missing error checking in
OE-core: in the custom distro case I was using MACHINE="quark" inside
one of the multiconfigs where I should have used "intel-quark".

Enhancement request filed:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=10810

-- 
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.