Bug 5205

Summary: meta-intel: some images fail to build -sdk image
Product: [Build System, Metadata & Runtime] Other YP Layers Reporter: Stoicescu Cornel <corneliux.stoicescu>
Component: layersAssignee: Paul Eggleton <bluelightning>
Status: VERIFIED FIXED QA Contact:
Severity: normal    
Priority: Medium+ CC: mark.hatle, poky.bs.watcher, poky.watcher
Version: 1.5   
Target Milestone: 1.5 M5   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: Regression (Used to work)
Verified: Documentation change: No (bug/feature does not impact docs)
Attachments:
Description Flags
autobuilder log for core-image-sato-sdk-chiefriver none

Description Stoicescu Cornel 2013-09-16 13:54:05 UTC
Created attachment 1501 [details]
autobuilder log for core-image-sato-sdk-chiefriver

poky master:566ca1e4769b4ec7e3f6c6a98bb817db2221cf82 (1.5 M5 RC1)
meta-intel master:4f5c753fb2db0cb1f6989ea3be270eebf3ea3572

The follwing tergets failed to build core-image-sato-sdk and core-image-lsb-sdk images: chiefriver, nuc, sugarbay

See attached for pasted output from autobuilder(they all fail the same way).
Comment 1 Paul Eggleton 2013-09-20 13:53:22 UTC
Looking at log.do_rootfs_install_packages_attemptonly I can see the problem:

error: libglib-2.0-utils-2.36.4-r0 requires /opt/poky/1.4+snapshot/sysroots/x86_64-pokysdk-linux/usr/bin/python

The libglib-2.0-utils package contains an errant #! line pointing to a version of python installed via buildtools (in this instance glib-2.0 was restored from sstate, but that's not especially important). It looks like the sed line already in the recipe might just need to be fixed up.
Comment 3 Stoicescu Cornel 2013-10-01 14:29:06 UTC
This issue is not present in latest 1.5 M5 RC5 build. Setting to VERIFIED for:
poky master:4d8ab87d25ea6e59dc88375813ef88ee0ac813d0