Bug 3915 - When building a multilib image, the results may not be consisten
Summary: When building a multilib image, the results may not be consisten
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: 1.4
Hardware: x86 Multiple
: Medium normal
Target Milestone: 1.4 M5
Assignee: Saul Wold
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2013-02-20 02:08 UTC by Mark Hatle
Modified: 2013-02-25 19:45 UTC (History)
2 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 Mark Hatle 2013-02-20 02:08:24 UTC 
When building a multilib image (i.e. lib32-core-image-basic) the results of the image creation change based on what was previously built.  It also does not ensure a primarily lib32 image!


Steps to reproduce:

setup you build directory

MACHINE = "qemux86-64"

PACKAGE_CLASSES = "package_rpm"

require conf/multilib.conf
MULTILIBS = "multilib:lib32"
DEFAULTTUNE_virtclass-multilib-lib32 = "x86"

(make sure this is a clean build directory!)

run:

bitbake lib32-core-image-basic

Look at the contents of the image, all packages used (and all of the files) are of the lib32- type.

run:

bitbake core-image-basic

Look at the contents of the image again, now all of the packages used (and all of the files) are of the 64-bit type.

run:

bitbake lib32-core-image-base

This time the filesystem is a mix of 32-bit and 64-bit packages and applications.  Due to the multiple copies of the libc, it is also significantly larger then it previously was.
Comment 1 Mark Hatle 2013-02-25 19:45:45 UTC 
Fixed in commit dfbb1aa184955923b85b81aabf944de8f1a1e4b5 (in oe-core)