[yocto] toolchain queries

[Khem Raj]

On Fri, Jul 15, 2011 at 2:13 PM, Kumar Gala <galak at kernel.crashing.org> wrote:
>
> On Jul 15, 2011, at 2:28 PM, Khem Raj wrote:
>
>> On Thu, Jul 14, 2011 at 7:36 PM, Kumar Gala <galak at kernel.crashing.org> wrote:
>>> Where is the best place to ask questions and try and get support for adding some toolchain variations in?
>>>
>>> I'm wanting to add support in for a few different flavors of PPC that are not currently supported:
>>>
>>> * e500v2 (gcc needs --enable-e500_double, eglibc
>>
>> this means ABI change especially due to double formats. This should be
>> doable in machine.conf
>> files or tune files.
>
> how so?  What can I set in there that would actually get passed into gcc's configure (not really seeing anything).  Also what exactly do you mean by a machine.conf

Well as I see not so easily which is since we share toolchain for
architectures and if
we let machines add ABI conflicting options then we will be in trouble
think of using
I could have suggested using something like GLIBC_EXTRA_OECONF but I
would not encourage that

So one way to go about this is that we use -gnuspe in target triplet
which will differentiate
SPE targets from classic ppc and then in gcc recipe include files

you can do something like

EXTRA_OECONF_append_linux-gnuspe = " --enable-e500_double "

>
>>> * e5500 (64-bit embedded ppc)
>>
>> this is new I guess. Its like adding a new arch to OE. See around
>> http://lists.linuxtogo.org/pipermail/openembedded-devel/2010-September/024661.html
>> is roughly what can be helpful in getting ppc64 going
>
> Thanks, will take a look at that.
>
> - k