Bug 8547 - update_icon_cache fails when using sstate and different build dir
Summary: update_icon_cache fails when using sstate and different build dir
Status: VERIFIED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: graphics (show other bugs)
Version: 1.9
Hardware: All Multiple
: High normal
Target Milestone: 2.0
Assignee: Ross Burton
QA Contact: Alexandru Georgescu
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2015-10-20 12:04 UTC by Ross Burton
Modified: 2015-11-06 15:28 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ross Burton 2015-10-20 12:04:34 UTC
WARNING: The postinstall intercept hook 'update_icon_cache' failed (exit code: 127)! See log for details!
WARNING: The postinstalls for the following packages will be postponed for first boot: adwaita-icon-theme sato-icon-theme connman-gnome
[log_check] WARNING: The postinstall intercept hook 'update_icon_cache' failed (exit code: 127)! See log for details!
[log_check] WARNING: The postinstalls for the following packages will be postponed for first boot: adwaita-icon-theme sato-icon-theme connman-gnome

The problem appears to be that the intercept isn't using the right paths.
Comment 1 Ross Burton 2015-10-20 12:48:59 UTC
And indeed the update_icon_cache intercept on a developer's machine that used sstate from the autobuilder has this:

STAGING_LIBDIR_NATIVE=/home/pokybuild/yocto-autobuilder/yocto-worker/ptest-x86/build/build/tmp/sysroots/x86_64-linux/usr/lib
Comment 2 Ross Burton 2015-10-20 16:35:45 UTC
Problem: the postinst has hard-coded the sysroot location but the postinst isn't mangled when building an image from sstate packages.
Comment 3 Ross Burton 2015-10-27 13:54:56 UTC
Fixed in oe-core 189d6232a2a9eb7192887b60f05b6643414a4ec6.
Comment 4 Costin 2015-11-06 15:28:53 UTC
Verified on latest master hash 9f734a262720d3f68f47854dd1c18da8e131bbfe on an Ubuntu 15.04 machine

Steps performed (thanks Ross):
1)source oe-init-build-env 1build && bitbake gdk-pixbuf -c cleansstate
2)bitbake core-image-sato
3)rm -rf 1build/
4)source oe-init-build-env 2build
5)bitbake core-image-sato

in my setup i used a common sstate dir by having:
SSTATE_DIR ?= "/media/sstate"