| Summary: | update_icon_cache fails when using sstate and different build dir | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Ross Burton <ross.burton> |
| Component: | graphics | Assignee: | Ross Burton <ross.burton> |
| Status: | VERIFIED FIXED | QA Contact: | Alexandru Georgescu <alexandru.c.georgescu> |
| Severity: | normal | ||
| Priority: | High | CC: | alexandru.c.georgescu, costin.c.constantin, meta.mr.watcher, meta.watcher |
| Version: | 1.9 | ||
| Target Milestone: | 2.0 | ||
| Hardware: | All | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Ross Burton
2015-10-20 12:04:34 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 Problem: the postinst has hard-coded the sysroot location but the postinst isn't mangled when building an image from sstate packages. Fixed in oe-core 189d6232a2a9eb7192887b60f05b6643414a4ec6. 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" |