[oe] [RFC} Disable multilib in gcc recipes

Khem Raj raj.khem at gmail.com
Sun Jul 4 17:52:45 UTC 2010


On Sun, Jul 4, 2010 at 6:59 AM, Detlef Vollmann <dv at vollmann.ch> wrote:
> On 07/02/10 00:01, Richard Purdie wrote:
>>
>> On Thu, 2010-07-01 at 00:14 -0700, Khem Raj wrote:
>>>
>>> I would like to propose to remove building multilib with gcc recipes.
>>> It creates problems
>>> and we do not package correct bits on some platforms. As we tend to
>>> build toolchains keeping in mind the machine it is targetting I think
>>> multilib is not that significant
>>>
>>> Concerns ? comments?
>>
>> I'm backing this. Currently multilib is broken and for a good
>> implementation we really needs a ground up proposal for how to handle it
>> well. I'm starting to look into the problem FWIW so I'd appreciate being
>> in the loop in any discussions.
>
> I've run into multilib issues as well, but could always solve it on a
> case by case base (e.g. on powerpc).  But I agree it's currently a mess.
> But what you need to keep in mind if you actually drop multilib support
> is that you need to rename the prefix for the SDK toolchains.
> It would be bad if PowerPC 32-bit and 64-bit toolchains were both named
> powerpc-angstrom-linux-

I think that does not happen. toolchain prefix is generally ${TARGET_ARCH}-x-x
for 64 bit powerpc TARGET_ARCH = "powerpc64"

>
>  Detlef
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel at lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>




More information about the Openembedded-devel mailing list