Bug 4799

Summary:	[Test Case 291] lib64 sato-sdk image should be built out with multilib support.
Product:	[Build System, Metadata & Runtime] OE-Core	Reporter:	Alexandru Palalau <alexandrux.palalau>
Component:	core	Assignee:	Saul Wold <sgw>
Status:	VERIFIED WORKSFORME	QA Contact:
Severity:	normal
Priority:	Medium	CC:	meta.mr.watcher, meta.watcher
Version:	1.5
Target Milestone:	1.5
Hardware:	x86
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	No (bug/feature does not impact docs)

Description Alexandru Palalau 2013-07-02 08:09:35 UTC

STATUS: FAILED
BUILD: master: 8e9501ffa8726d69412d669580d787ffedb88d34
ENVIRONMENT: Fedora 17
STEPS TO REPRODUCE: 1. Prepare poky build environment
2. by following https://wiki.pokylinux.org/wiki/Multilib, set local.conf to enable multilib build and set MACHINE to qemux86 as following:
#####
MACHINE = "qemux86"
require conf/multilib.conf
MULTILIBS = "multilib:lib64"
DEFAULTTUNE_virtclass-multilib-lib64 = "x86-64"
#####
3. with rpm set for package format, build lib64-core-sato-sdk image
4. after build finished, start up the image and the kernel should not be able to boot

EXPECTED OUTCOME: lib64 sato-sdk image should be built out with multilib support.

ACTUAL OUTCOME: The image is able to boot up. Same for lsb-sdk and sato images
  

Build Configuration:
BB_VERSION        = "1.19.1"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "Fedora-17"
TARGET_SYS        = "i586-poky-linux"
MACHINE           = "qemux86"
DISTRO            = "poky"
DISTRO_VERSION    = "1.4+snapshot-20130701"
TUNE_FEATURES     = "m32 i586"
TARGET_FPU        = ""
meta              
meta-yocto        
meta-yocto-bsp    = "(nobranch):8e9501ffa8726d69412d669580d787ffedb88d34"

Comment 1 Saul Wold 2013-07-09 16:39:07 UTC

Not sure this is a valid configuration, I need to investigate

Comment 2 Saul Wold 2013-07-09 20:26:00 UTC

Ok, I tried this and indeed it does not boot, I tried core-image-sato and 
core-image-sato-sdk, both filed to boot as the test case sez.

This was with post M2 rc1

Comment 3 Alexandru Palalau 2013-07-10 13:22:49 UTC

Re-checked with latest master and also with initial commit ID.
The image could not be started, as expected.
Maybe it had something to do with sstate, as now I checked with clean build dir.

Comment 4 Alexandru Palalau 2013-09-25 14:50:59 UTC

Switching to verified, as I should have done already per last comment.