[OE-core] GCC 4.9 and Morty

[Lee, Yong]

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].

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.

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.khem at gmail.com] 
Sent: Tuesday, October 24, 2017 12:26 PM
To: Lee, Yong <Yong.Lee at johnsonoutdoors.com>
Cc: openembedded-core at 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.Lee at 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 at 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,
-------------- next part --------------
A non-text attachment was scrubbed...
Name: bitbake_gcc.error
Type: application/octet-stream
Size: 8655 bytes
Desc: bitbake_gcc.error
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20171024/c3f6782b/attachment-0004.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gcc.diff
Type: application/octet-stream
Size: 1152 bytes
Desc: gcc.diff
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20171024/c3f6782b/attachment-0005.obj>