Bug 4602 - [Autobuilder] smart can't install gdb because of liblzma
Summary: [Autobuilder] smart can't install gdb because of liblzma
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: devtools / tool chain (show other bugs)
Version: 1.5
Hardware: x86 Multiple
: Medium normal
Target Milestone: 1.5
Assignee: Saul Wold
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2013-06-04 07:05 UTC by Bogdan Marinescu
Modified: 2013-06-04 17:00 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Bogdan Marinescu 2013-06-04 07:05:41 UTC 
http://autobuilder.yoctoproject.org:8011/builders/build-appliance/builds/155/steps/Building%20Images_1/logs/stdio

 
| Note: configuring RPM cross-install scriptlet_wrapper
| 
| Updating cache... ######################################## [100%]
| 
| Saving cache...
| 
| Note: adding Smart RPM DB channel
| 
| Note: to be installed: psplash@x86_64 packagegroup-self-hosted@all packagegroup-core-x11-base@all smartpm@x86_64 packagegroup-core-ssh-openssh@all rpm@x86_64 packagegroup-core-boot@qemux86_64 locale-base-en-us@x86_64 locale-base-en-gb@x86_64
| Loading cache...
| Updating cache... ######################################## [100%]
| 
| Computing transaction...error: Can't install gdb-7.6-r0@x86_64: no package provides liblzma.so.5(XZ_5.0)(64bit)
| 
| Saving cache...
| 
| ERROR: Function failed: do_rootfs (log file is located at /srv/home/pokybuild/yocto-autobuilder-new/yocto-slave/build-appliance/build/build/tmp/work/qemux86_64-poky-linux/build-appliance-image/8.0-r0/temp/log.do_rootfs.20578)
ERROR: Task 8 (/srv/home/pokybuild/yocto-autobuilder-new/yocto-slave/build-appliance/build/meta/recipes-core/images/build-appliance-image_8.0.bb, do_rootfs) failed with exit code '1'
Summary: There was 1 ERROR message shown, returning a non-zero exit code.
Comment 1 Mark Hatle 2013-06-04 13:27:36 UTC 
Looking at the log, this appears to be a host contamination problem with gdb.

Unless liblzma.so is available in the main build, it's being picked up from the host improperly.
Comment 2 Mark Hatle 2013-06-04 13:28:53 UTC 
Moving domain to 'development'  (I assume this covers the toolchain components?)

If not, it should be moved to runtime or another area.