Bug 6298

Summary:	To enable 64-bit target machine booted with sato-sdk image to compile 32-bit application
Product:	[Runtime] General Runtime	Reporter:	Ong Boon Leong <boon.leong.ong>
Component:	General Runtime	Assignee:	Saul Wold <sgw>
Status:	RESOLVED NOTABUG	QA Contact:
Severity:	enhancement
Priority:	Medium	CC:	boon.leong.ong
Version:	1.7
Target Milestone:	1.8
Hardware:	All
OS:	x86_64
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	No (bug/feature does not impact docs)

Description Ong Boon Leong 2014-05-08 16:23:30 UTC

This is a new request from DCG/CSIG PAE, "Schuetze, Joel D <joel.d.schuetze@intel.com>". I am filling in the request on his behalf.

The request to enable 64-bit core-image-sato-sdk image to support 32-bit application build when the image is booted on target machine. 

Often there is legacy application that has been fully validated on older version and customer will like carry them over without making them as 64-bit. So, this type of customers would want to use the tool-chain provided on target machine to compile 32-bit application even though the system is 64-bit.

Comment 1 Saul Wold 2014-05-08 23:43:10 UTC

Does the existing multi-lib support not support this?  Please base on to Joel 
to enable Multi-lib support with lib32 libraries as follows:

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

This should build the lib32 libraries also.

We do this regularly on the autobuilder, please check the documentation.

Comment 2 Saul Wold 2014-11-11 21:32:09 UTC

Can you update this or I will close this, does multi-lib not support what Joel 
wants?

Comment 3 Ong Boon Leong 2014-11-12 02:23:21 UTC

Thanks Saul. For now, I think that we are good in this part. We can close that.

Comment 4 Ong Boon Leong 2014-11-12 02:24:39 UTC

I have changed this to resolved and not a bug. Thanks