Bug 6534

Summary:	Does the Yocto Project toolchain support 'multilib' (within the toolchain)?
Product:	[Build System, Metadata & Runtime] OE-Core	Reporter:	baoshan <pangbw>
Component:	devtools / tool chain	Assignee:	Mark Hatle <mark.hatle>
Status:	RESOLVED INVALID	QA Contact:
Severity:	normal
Priority:	Medium	CC:	meta.mr.watcher, meta.watcher, poky.bs.watcher, poky.watcher, richard.purdie
Version:	1.7
Target Milestone:	1.7
Hardware:	x86
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	Yes (doc changes required)

Description baoshan 2014-07-14 22:18:02 UTC

I am trying to build gcc-cross in 'multilib' mode under Yocto, I have tried many methods but without luck, I looked into the code and feel the 'multilib' is NOT supported at all though we can find some receipt files in the Yocto source tree. 

Can someone tell me if 'multilib' is supported or not at this point? If it is, please give me a simple steps to show how to do that.

Thanks,
Baoshan

Comment 1 Mark Hatle 2014-07-17 14:54:32 UTC

There are two difference concepts of the multilib within the Yocto Project.

The primary usage is multiple toolchains (one per multilib) and multilib sysroots (again one per multilib).


'gcc-cross' does not support multilib configuration from what I understand.  The question should really be about gcc-cross-canadian (this is the toolchain that is located within the generated SDK.)


I believe the question is -- how are multilibs, within GCC enabled and used?  My understanding is that baoshan wants to generate an SDK that uses a single gcc binary with multilibs enabled.

Comment 2 Richard Purdie 2014-12-11 16:29:50 UTC

If the question is whether we plan to make gcc-cross support multilib, we do not, that isn't the way multilib support in OE works. This isn't something we plan to change and the bug resolution would be WONTFIX.

On the other hand, our builds do support multilib, as do our SDK and gcc-cross-canadian and so on so that would be WORKSFORME.

If there is a specific issue to address please open a new bug or reopen this with the details.