On Tue, Oct 24, 2017 at 10:33 AM, Lee, Yong
<yong....@johnsonoutdoors.com> wrote:
> Thanks Raj for the input. Attached the logs. Please take a look.
> The .diff file is based on the toolchain-linaro.inc file shipped with TI's 
> SDK [1].
>

Your changes look fine.

> I will try to configure the SDK to use the internal toolchain and see if I 
> can decouple myself from the external toolchain to simplify things.
>

you might have to bug your SDK provider for gcc 4.9 build issue


> Adam
>
> [1] 
> http://arago-project.org/git/?p=meta-arago.git;a=blob;f=meta-arago-distro/conf/distro/include/toolchain-linaro.inc;h=20a65174f269c1e1a5984c5476a2ab4e5dfc42b5;hb=refs/heads/morty
>
> -----Original Message-----
> From: Khem Raj [mailto:raj.k...@gmail.com]
> Sent: Tuesday, October 24, 2017 12:26 PM
> To: Lee, Yong <yong....@johnsonoutdoors.com>
> Cc: openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core] GCC 4.9 and Morty
>
> *EXTERNAL EMAIL*
>
>
> On Tue, Oct 24, 2017 at 6:56 AM, Lee, Yong <yong....@johnsonoutdoors.com> 
> wrote:
>> I have a bunch of apps that require an old version of GCC (4.9 or less).
>>
>> There are a few versions of GCC available in my Morty based SDK.
>>
>>
>>
>> build@6e35408e8fa5:~/tisdk/build$ bitbake-layers show-recipes gcc
>>
>> WARNING: No recipes available for:
>>
>>
>> /home/build/tisdk/sources/meta-openamp/recipes-bsp/device-tree/device-
>> tree-generation_%.bbappend
>>
>> Parsing recipes..done.
>>
>> === Matching recipes: ===
>>
>> gcc:
>>
>>   meta-linaro-toolchain linaro-4.9
>>
>>   meta-linaro-toolchain linaro-6.2
>>
>>   meta                 6.2.0
>>
>>   meta                 5.4.0
>>
>>   meta-linaro-toolchain linaro-5.3
>>
>>   meta-linaro-toolchain linaro-5.2
>>
>>
>>
>> Immediately I have set the PREFERRED_VERSION of gcc to 4.9 but bitbake
>> does not go beyond configuration.
>>
>>
>
> Please post the error and change you did to enable 4.9
>
>>
>> I believe 4.9 + morty combination has not been tested at all. I
>> understand my apps need to get updated, but that’s not my call.
>
> OE-core and yocto releases by default do not test toolchains coming from 
> other layers so essentially 6.2 is whats the default compiler with morty and 
> thats what is most tested however, others might have tested the other 
> combinations with morty,
-- 
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Reply via email to