Bug 12102

Summary: eSDK fails to build for linux-yocto-custom
Product: [Yocto Project Subprojects] eSDK Reporter: Lukasz Majewski <lukma633>
Component: eSDKAssignee: Paul Eggleton <bluelightning>
Status: RESOLVED WONTFIX QA Contact: Francisco Pedraza <francisco.j.pedraza.gonzalez>
Severity: critical    
Priority: Medium CC: l.majewski, randy.macleod
Version: unspecified   
Target Milestone: 2.3.5   
Hardware: Other   
OS: arm   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Don't know
Attachments:
Description Flags
eSDK build log
none
Build environment description
none
Ext SDK error log after building none

Description Lukasz Majewski 2017-09-19 08:32:33 UTC 
Created attachment 4012 [details]
eSDK build log

I'm trying to build eSDK for my BSP (which also creates initramfs image for my kernel):

bitbake -c do_populate_sdk_ext core-image-XXX

Error excerpt:
--------------
NOTE: Executing RunQueue Tasks
ERROR: Task linux-yocto-custom.do_fetch attempted to execute unexpectedly
ERROR: Task linux-yocto-custom.do_unpack attempted to execute unexpectedly
ERROR: Task linux-yocto-custom.do_kernel_checkout attempted to execute unexpectedly
ERROR: Task linux-yocto-custom.do_validate_branches attempted to execute unexpectedly
ERROR: Task linux-yocto-custom.do_kernel_metadata attempted to execute unexpectedly
ERROR: Task linux-yocto-custom.do_patch attempted to execute unexpectedly
ERROR: Task linux-yocto-custom.do_prepare_recipe_sysroot attempted to execute unexpectedly
ERROR: Task linux-yocto-custom.do_kernel_configme attempted to execute unexpectedly
ERROR: Task linux-yocto-custom.do_configure attempted to execute unexpectedly
ERROR: Task linux-yocto-custom.do_kernel_configcheck attempted to execute unexpectedly
ERROR: Task linux-yocto-custom.do_kernel_version_sanity_check attempted to execute unexpectedly
ERROR: Task linux-yocto-custom.do_compile attempted to execute unexpectedly
ERROR: Task linux-yocto-custom.do_compile_kernelmodules attempted to execute unexpectedly
ERROR: Task linux-yocto-custom.do_kernel_link_images attempted to execute unexpectedly
ERROR: Task linux-yocto-custom.do_strip attempted to execute unexpectedly
ERROR: Task linux-yocto-custom.do_assemble_fitimage attempted to execute unexpectedly
ERROR: Task linux-yocto-custom.do_sizecheck attempted to execute unexpectedly
ERROR: Task linux-yocto-custom.do_install attempted to execute unexpectedly
ERROR: Task linux-yocto-custom.do_bundle_initramfs attempted to execute unexpectedly
NOTE: Tasks Summary: Attempted 4343 tasks of which 4343 didn't need to be rerun and all succeeded.

Summary: There was 1 WARNING message shown.
Summary: There were 19 ERROR messages shown, returning a non-zero exit code.


diffsigs output:
----------------

bitbake-diffsigs -t linux-yocto-custom do_bundle_initramfs
ERROR: Only one matching sigdata file found for the specified task (linux-yocto-custom do_bundle_initramfs)

Note:
-----

If this helps - there was similar issue already reported:
http://lists.openembedded.org/pipermail/openembedded-core/2016-July/123886.html

The author says that commenting out INITRAMFS_IMAGE helped.

However, I've been trying:
SDK_LOCAL_CONF_BLACKLIST_append = " INITRAMFS_IMAGE"
or
SDK_INHERIT_BLACKLIST_append = " kernel"

added to my distro.conf file. Both did not solve this issue.


Version info:
-------------

Build Configuration:
BB_VERSION        = "1.34.0"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "universal"
TARGET_SYS        = "arm-poky-linux-gnueabi"
MACHINE           = "XXX"
DISTRO            = "YYY-distro"
DISTRO_VERSION    = "2.3.1"
TUNE_FEATURES     = "arm armv7a vfp thumb neon callconvention-hard"
TARGET_FPU        = "hard"
meta              
meta-poky         = "pyro:6bd890d9e011014cf323e61267f8b256949d44aa"


Please find also detailed build log.
Comment 1 Lukasz Majewski 2017-09-19 09:24:08 UTC 
I can confirm that after commenting out:

#INITRAMFS_IMAGE ?= "${MACHINE}-image-initramfs-content"

The eSDK is build correctly.
Comment 2 Lukasz Majewski 2017-09-19 09:26:10 UTC 
I can confirm that after commenting out:

#INITRAMFS_IMAGE ?= "${MACHINE}-image-initramfs-content"

The eSDK is build correctly.
Comment 3 Paul Eggleton 2017-09-22 04:37:15 UTC 
I believe this is fixed in master - and it's relatively easy to backport to pyro. Could you please give the following patch a try and confirm that it fixes the issue for you as well?

http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=paule/pyro-initramfs-fix&id=00539c6b21731e54120d98ddc9d2ab582defdf69
Comment 4 Lukasz Majewski 2017-09-22 09:16:30 UTC 
(In reply to comment #3)
> I believe this is fixed in master - and it's relatively easy to backport to
> pyro. Could you please give the following patch a try and confirm that it
> fixes the issue for you as well?
> 
> http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=paule/pyro-
> initramfs-fix&id=00539c6b21731e54120d98ddc9d2ab582defdf69

I can confirm that after backporting this patch I'm able to execute

bitbake -c populate_sdk_ext core-image-XXX

without errors.

However, when I do install the produced eSDK itself I see following warnings:

WARNING: The linux-yocto-custom:do_assemble_fitimage_initramfs sig is computed to be 80e8f04b6c3d6ca054ead9f7f1c5054d, but the sig is locked to d3c7ef5f1feb723b45ace36e6e9886d8 in SIGGEN_LOCKEDSIGS_t-display5
The linux-yocto-custom:do_bundle_initramfs sig is computed to be 9efd9829144147b03cb88fa7948c007a, but the sig is locked to 6c769c56ec24c2a20ef24c2a904c3df8 in SIGGEN_LOCKEDSIGS_t-display5
Comment 5 Paul Eggleton 2017-09-25 11:24:08 UTC 
Indeed, I saw the same thing as well - I've just sent this to fix it:

http://cgit.openembedded.org/openembedded-core-contrib/commit/?h=paule/esdk-sigs-fix
Comment 6 Paul Eggleton 2017-09-26 20:44:51 UTC 
OK, the aforementioned patch has been merged. I have just sent backports to pyro:

http://cgit.openembedded.org/openembedded-core-contrib/log/?h=paule/pyro-esdk-initramfs-fix-oe
Comment 8 Armin Kuster 2018-02-15 16:01:53 UTC 
should be fixed now
Comment 9 Lukasz Majewski 2018-02-16 15:37:09 UTC 
Created attachment 4211 [details]
Build environment description

Information regarding build environment
Comment 10 Lukasz Majewski 2018-02-16 15:38:00 UTC 
Created attachment 4212 [details]
Ext SDK error log after building

The build error after building
Comment 11 Lukasz Majewski 2018-02-16 15:39:40 UTC 
The bitbake -c populate_sdk core-image-XXX is still not working.
Comment 12 Armin Kuster 2018-02-22 03:57:16 UTC 
(In reply to comment #11)
> The bitbake -c populate_sdk core-image-XXX is still not working.

ok. thanks for checking. I am going to try to reproduce this
Comment 13 Armin Kuster 2018-06-10 22:53:11 UTC 
I have not time to look into this.
Comment 14 Paul Eggleton 2018-08-31 04:24:00 UTC 
Unfortunately at this point we're not going to fix this in the 2.3 branch which is no longer supported. I'm pretty confident we have fixed this in later releases. If you do see anything like it in a supported release please reopen.