Bug 2216 - [multilib] core-image-sato ipk build failed due to dependency of lib32-ofono
Summary: [multilib] core-image-sato ipk build failed due to dependency of lib32-ofono
Status: VERIFIED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: High major
Target Milestone: 1.2 M4
Assignee: Lianhao Lu
QA Contact:
URL:
Whiteboard: (1.2)
: 1899 (view as bug list)
Depends on:
Blocks:
 
Reported: 2012-03-31 08:51 UTC by Jiajun Xu
Modified: 2012-04-22 15:11 UTC (History)
7 users (show)

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

Attachments
log for do_rootfs (130.32 KB, text/plain)
2012-03-31 08:51 UTC, Jiajun Xu 		no flags Details
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 Jiajun Xu 2012-03-31 08:51:37 UTC 
Created attachment 425 [details]
log for do_rootfs

tree/branch: poky/1.2_M4
commit: da6233ea034f35eff59306fdad31f318c340c359

With 1.2 M4 branch, if I choose ipk format to build a multilib enabled core-imaeg-sato image, it will report fail during do_rootfs for image.
The error log is as below. Details could be found in attachment.

The configuration I used for the build is like below:
########
MACHINE = "qemux86-64"
PACKAGE_CLASSES ?= "package_ipk"
require conf/multilib.conf
MULTILIBS = "multilib:lib32"
DEFAULTTUNE_virtclass-multilib-lib32 = "x86"
IMAGE_INSTALL_append = "lib32-connman-gnome"
########

########
Configuring xf86-video-vmware.
Configuring xset.
Configuring xrandr.
Configuring task-core-x11-base.
Collected errors:
 * satisfy_dependencies_for: Cannot satisfy the following dependencies for lib32-connman-gnome:
 *      lib32-ofono *
 * opkg_install_cmd: Cannot install package lib32-connman-gnome.
########
Comment 1 Lianhao Lu 2012-04-05 15:07:38 UTC 
*** Bug 1899 has been marked as a duplicate of this bug. ***
Comment 4 Jiajun Xu 2012-04-22 15:11:18 UTC 
Verify the bug as fixed in 1.2 M4 RC4 testing.