[oe] Found offending commit: oe-core: 7267e7c000c76c44d09835d4cd2bc485b6a39a2a (was Re: [meta-oe] add-layers fails with python error)

[Daniel F. Dickinson]

On 23/01/18 04:19 AM, Daniel F. Dickinson wrote:
> On 23/01/18 02:30 AM, Daniel F. Dickinson wrote:
>> On 23/01/18 01:50 AM, Daniel F. Dickinson wrote:
>>> I'm not sure which list this belongs on, but since it's an attempt to 
>>> use meta-oe that triggers the error, I post it here.  I've seen 
>>> others reporting this issue prior to this, so perhaps it's related to 
>>> the build environment?  (I'm on Debian 9).
>>>
>>> Steps:
>>>
>>> Checkout bitbake branch 1.34 (also occurs with 1.32 & 1.36)
>>> Checkout oe-core master (also occurs with rocko)
>>> Checkout meta-openembedded master (also occurs with rocko)
>>>
>>> source oe-init-env
>>>
>>> bitbake-layers add-layer /path/to/meta-openembedded/meta-oe
>>>
>> [snip]
>>
>> Seems this is actually a core issue (bitbake -c listtasks
>> with only core's autogenerated build dir gives a similar,
>> but shorter, traceback).
>>
>> Perhaps it's significant that I see:
>>
>>
>> LAYERVERSION_core = "11" in oe-core/meta/layers.conf
>> and LCONF_VERSION = "7" in build/bblayers.conf?
>>
> FYI git version f43290f6e302dbacf5581d1fe1c6c991dd387779 works (I had a 
> previous checkout with that version, which was working,so I guess I'll 
> try git bisect.
> 

Error is in core; I guess I'll join the core list and let them know...

7267e7c000c76c44d09835d4cd2bc485b6a39a2a is the first bad commit
commit 7267e7c000c76c44d09835d4cd2bc485b6a39a2a
Author: Richard Purdie <richard.purdie at linuxfoundation.org>
Date:   Thu Jul 6 12:54:15 2017 +0100

     base: Add MultiConfigParsed handler to deal with unstable build 
signatures

     This uses the newly added MultiConfigParsed event to handle 
problems where
     checksums in multiconfig build were not fuctioning as expected.

     The issue arises around SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS which contains
     entries like:

     * gcc-cross-${TARGET_ARCH}->virtual/${TARGET_PREFIX}libc-for-gcc
     * gcc-cross-${TARGET_ARCH}->linux-libc-headers

     These need to be expanded in the multiconfig data store but then placed
     into the shared main datastore used by the siggen code. The only other
     alternative would be a siggen instance for each multiconfig however 
that
     seemed even more complex and invasive.

     In real world usage, this issue would mean a qemux86 base config with
     other armv5 and armv7 configs (e.g. beaglebone and qemuarm) would
     try and build gcc-cross twice since dependencies normaly excluded
     (e.g. linux-libc-headers) would now be included. This breaks sstate 
reuse
     as well as breaking builds unless separate tmpdirs are used.

     This patch adds all the entries for each multiconfig. Whilst there may
     be duplicates, this shouldn't be an issue.

     Signed-off-by: Richard Purdie <richard.purdie at linuxfoundation.org>