[meta-arago,oe-layersetup] oe-layersetup: configs: add meta-clang into the kirkstone configs

From: Darren Etheridge <detheridge@ti.com>

Add meta-clang into the 3 kirkstone configs.  meta-clang is pinned to
the kirkstone-clang12 branch because this is what we will be using for
the chromium v111 browser build.

We want to pull meta-clang into all kirkstone builds even without
chromium so that we find any integration problems that clang might
introduce even before we start doing the much larger chromium builds.

Signed-off-by: Darren Etheridge <detheridge@ti.com>
---
 configs/arago-kirkstone-config.txt      | 2 +-
 configs/arago-kirkstone-next-config.txt | 2 +-
 configs/arago-kirkstone-wip-config.txt  | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

On 2/8/24 13:14, detheridge@ti.com wrote:
> From: Darren Etheridge <detheridge@ti.com>
> 
> Add meta-clang into the 3 kirkstone configs.  meta-clang is pinned to
> the kirkstone-clang12 branch because this is what we will be using for
> the chromium v111 browser build.
> 
> We want to pull meta-clang into all kirkstone builds even without
> chromium so that we find any integration problems that clang might
> introduce even before we start doing the much larger chromium builds.
> 
> Signed-off-by: Darren Etheridge <detheridge@ti.com>
> ---
>   configs/arago-kirkstone-config.txt      | 2 +-
>   configs/arago-kirkstone-next-config.txt | 2 +-
>   configs/arago-kirkstone-wip-config.txt  | 2 +-
>   3 files changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/configs/arago-kirkstone-config.txt b/configs/arago-kirkstone-config.txt
> index ceb8d74..43a8a0b 100644
> --- a/configs/arago-kirkstone-config.txt
> +++ b/configs/arago-kirkstone-config.txt
> @@ -9,7 +9,7 @@ meta-virtualization,https://git.yoctoproject.org/meta-virtualization,kirkstone,H
>   meta-openembedded,https://git.openembedded.org/meta-openembedded,kirkstone,HEAD,layers=meta-networking:meta-python:meta-oe:meta-gnome:meta-filesystems
>   meta-ti,https://git.yoctoproject.org/meta-ti,kirkstone,HEAD,layers=meta-ti-extras:meta-ti-bsp
>   meta-arm,https://git.yoctoproject.org/meta-arm,kirkstone,HEAD,layers=meta-arm:meta-arm-toolchain
> -#meta-clang,https://github.com/kraj/meta-clang,kirkstone,HEAD,layers=
> +meta-clang,https://github.com/kraj/meta-clang,kirkstone-clang12,HEAD,layers=
>   oe-core,https://git.openembedded.org/openembedded-core,kirkstone,HEAD,layers=meta
>   OECORELAYERCONF=./sample-files/bblayers.conf.sample
>   OECORELOCALCONF=./sample-files/local-arago64-v2.conf.sample
> diff --git a/configs/arago-kirkstone-next-config.txt b/configs/arago-kirkstone-next-config.txt
> index dcf935d..9d173df 100644
> --- a/configs/arago-kirkstone-next-config.txt
> +++ b/configs/arago-kirkstone-next-config.txt
> @@ -17,7 +17,7 @@ meta-virtualization,https://git.yoctoproject.org/meta-virtualization,kirkstone,H
>   meta-openembedded,https://git.openembedded.org/meta-openembedded,kirkstone,HEAD,layers=meta-networking:meta-python:meta-oe:meta-gnome:meta-filesystems
>   meta-ti,https://git.yoctoproject.org/meta-ti,kirkstone-next,HEAD,layers=meta-ti-extras:meta-ti-bsp
>   meta-arm,https://git.yoctoproject.org/meta-arm,kirkstone,HEAD,layers=meta-arm:meta-arm-toolchain
> -#meta-clang,https://github.com/kraj/meta-clang,kirkstone,HEAD,layers=
> +meta-clang,https://github.com/kraj/meta-clang,kirkstone-clang12,HEAD,layers=
>   oe-core,https://git.openembedded.org/openembedded-core,kirkstone,HEAD,layers=meta
>   OECORELAYERCONF=./sample-files/bblayers.conf.sample
>   OECORELOCALCONF=./sample-files/local-arago64-v2.conf.sample
> diff --git a/configs/arago-kirkstone-wip-config.txt b/configs/arago-kirkstone-wip-config.txt
> index 9dd72ab..dfe8bd6 100644
> --- a/configs/arago-kirkstone-wip-config.txt
> +++ b/configs/arago-kirkstone-wip-config.txt
> @@ -9,7 +9,7 @@ meta-virtualization,https://git.yoctoproject.org/meta-virtualization,kirkstone,H
>   meta-openembedded,https://git.openembedded.org/meta-openembedded,kirkstone,HEAD,layers=meta-networking:meta-python:meta-oe:meta-gnome:meta-filesystems
>   meta-ti,https://git.yoctoproject.org/meta-ti,kirkstone-wip,HEAD,layers=meta-ti-extras:meta-ti-bsp
>   meta-arm,https://git.yoctoproject.org/meta-arm,kirkstone,HEAD,layers=meta-arm:meta-arm-toolchain
> -#meta-clang,https://github.com/kraj/meta-clang,kirkstone,HEAD,layers=
> +meta-clang,https://github.com/kraj/meta-clang,kirkstone-clang12,HEAD,layers=
>   oe-core,https://git.openembedded.org/openembedded-core,kirkstone,HEAD,layers=meta
>   OECORELAYERCONF=./sample-files/bblayers.conf.sample
>   OECORELOCALCONF=./sample-files/local-arago64-v2.conf.sample

Just a heads up, not sure if this can be picked up as is because of 
legacy devices having issues with meta-clang. It may not be a problem 
anymore but I remember that was what provoked the initial removal of 
meta-clang back around 9.1. Darren's running some tests.

On 2/8/2024 1:34 PM, Randolph Sapp wrote:
> On 2/8/24 13:14, detheridge@ti.com wrote:
>> From: Darren Etheridge <detheridge@ti.com>
>>
>> Add meta-clang into the 3 kirkstone configs.  meta-clang is pinned to
>> the kirkstone-clang12 branch because this is what we will be using for
>> the chromium v111 browser build.
>>
>> We want to pull meta-clang into all kirkstone builds even without
>> chromium so that we find any integration problems that clang might
>> introduce even before we start doing the much larger chromium builds.
>>
>> Signed-off-by: Darren Etheridge <detheridge@ti.com>
>> ---
>>   configs/arago-kirkstone-config.txt      | 2 +-
>>   configs/arago-kirkstone-next-config.txt | 2 +-
>>   configs/arago-kirkstone-wip-config.txt  | 2 +-
>>   3 files changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/configs/arago-kirkstone-config.txt 
>> b/configs/arago-kirkstone-config.txt
>> index ceb8d74..43a8a0b 100644
>> --- a/configs/arago-kirkstone-config.txt
>> +++ b/configs/arago-kirkstone-config.txt
>> @@ -9,7 +9,7 @@ 
>> meta-virtualization,https://git.yoctoproject.org/meta-virtualization,kirkstone,H
>>   
>> meta-openembedded,https://git.openembedded.org/meta-openembedded,kirkstone,HEAD,layers=meta-networking:meta-python:meta-oe:meta-gnome:meta-filesystems
>>   
>> meta-ti,https://git.yoctoproject.org/meta-ti,kirkstone,HEAD,layers=meta-ti-extras:meta-ti-bsp
>>   
>> meta-arm,https://git.yoctoproject.org/meta-arm,kirkstone,HEAD,layers=meta-arm:meta-arm-toolchain
>> -#meta-clang,https://github.com/kraj/meta-clang,kirkstone,HEAD,layers=
>> +meta-clang,https://github.com/kraj/meta-clang,kirkstone-clang12,HEAD,layers=
>>   
>> oe-core,https://git.openembedded.org/openembedded-core,kirkstone,HEAD,layers=meta
>>   OECORELAYERCONF=./sample-files/bblayers.conf.sample
>>   OECORELOCALCONF=./sample-files/local-arago64-v2.conf.sample
>> diff --git a/configs/arago-kirkstone-next-config.txt 
>> b/configs/arago-kirkstone-next-config.txt
>> index dcf935d..9d173df 100644
>> --- a/configs/arago-kirkstone-next-config.txt
>> +++ b/configs/arago-kirkstone-next-config.txt
>> @@ -17,7 +17,7 @@ 
>> meta-virtualization,https://git.yoctoproject.org/meta-virtualization,kirkstone,H
>>   
>> meta-openembedded,https://git.openembedded.org/meta-openembedded,kirkstone,HEAD,layers=meta-networking:meta-python:meta-oe:meta-gnome:meta-filesystems
>>   
>> meta-ti,https://git.yoctoproject.org/meta-ti,kirkstone-next,HEAD,layers=meta-ti-extras:meta-ti-bsp
>>   
>> meta-arm,https://git.yoctoproject.org/meta-arm,kirkstone,HEAD,layers=meta-arm:meta-arm-toolchain
>> -#meta-clang,https://github.com/kraj/meta-clang,kirkstone,HEAD,layers=
>> +meta-clang,https://github.com/kraj/meta-clang,kirkstone-clang12,HEAD,layers=
>>   
>> oe-core,https://git.openembedded.org/openembedded-core,kirkstone,HEAD,layers=meta
>>   OECORELAYERCONF=./sample-files/bblayers.conf.sample
>>   OECORELOCALCONF=./sample-files/local-arago64-v2.conf.sample
>> diff --git a/configs/arago-kirkstone-wip-config.txt 
>> b/configs/arago-kirkstone-wip-config.txt
>> index 9dd72ab..dfe8bd6 100644
>> --- a/configs/arago-kirkstone-wip-config.txt
>> +++ b/configs/arago-kirkstone-wip-config.txt
>> @@ -9,7 +9,7 @@ 
>> meta-virtualization,https://git.yoctoproject.org/meta-virtualization,kirkstone,H
>>   
>> meta-openembedded,https://git.openembedded.org/meta-openembedded,kirkstone,HEAD,layers=meta-networking:meta-python:meta-oe:meta-gnome:meta-filesystems
>>   
>> meta-ti,https://git.yoctoproject.org/meta-ti,kirkstone-wip,HEAD,layers=meta-ti-extras:meta-ti-bsp
>>   
>> meta-arm,https://git.yoctoproject.org/meta-arm,kirkstone,HEAD,layers=meta-arm:meta-arm-toolchain
>> -#meta-clang,https://github.com/kraj/meta-clang,kirkstone,HEAD,layers=
>> +meta-clang,https://github.com/kraj/meta-clang,kirkstone-clang12,HEAD,layers=
>>   
>> oe-core,https://git.openembedded.org/openembedded-core,kirkstone,HEAD,layers=meta
>>   OECORELAYERCONF=./sample-files/bblayers.conf.sample
>>   OECORELOCALCONF=./sample-files/local-arago64-v2.conf.sample
> 
> Just a heads up, not sure if this can be picked up as is because of 
> legacy devices having issues with meta-clang. It may not be a problem 
> anymore but I remember that was what provoked the initial removal of 
> meta-clang back around 9.1. Darren's running some tests.

I was going to ask if these had been addressed yet...

On 2/8/2024 1:40 PM, Ryan Eatmon wrote:
> 
> 
> On 2/8/2024 1:34 PM, Randolph Sapp wrote:
>> On 2/8/24 13:14, detheridge@ti.com wrote:
>>> From: Darren Etheridge <detheridge@ti.com>
>>>
>>> Add meta-clang into the 3 kirkstone configs.  meta-clang is pinned to
>>> the kirkstone-clang12 branch because this is what we will be using for
>>> the chromium v111 browser build.
>>>
>>> We want to pull meta-clang into all kirkstone builds even without
>>> chromium so that we find any integration problems that clang might
>>> introduce even before we start doing the much larger chromium builds.
>>>
>>> Signed-off-by: Darren Etheridge <detheridge@ti.com>
>>> ---
>>>   configs/arago-kirkstone-config.txt      | 2 +-
>>>   configs/arago-kirkstone-next-config.txt | 2 +-
>>>   configs/arago-kirkstone-wip-config.txt  | 2 +-
>>>   3 files changed, 3 insertions(+), 3 deletions(-)
>>>
>>> diff --git a/configs/arago-kirkstone-config.txt 
>>> b/configs/arago-kirkstone-config.txt
>>> index ceb8d74..43a8a0b 100644
>>> --- a/configs/arago-kirkstone-config.txt
>>> +++ b/configs/arago-kirkstone-config.txt
>>> @@ -9,7 +9,7 @@ 
>>> meta-virtualization,https://git.yoctoproject.org/meta-virtualization,kirkstone,H
>>> meta-openembedded,https://git.openembedded.org/meta-openembedded,kirkstone,HEAD,layers=meta-networking:meta-python:meta-oe:meta-gnome:meta-filesystems
>>> meta-ti,https://git.yoctoproject.org/meta-ti,kirkstone,HEAD,layers=meta-ti-extras:meta-ti-bsp
>>> meta-arm,https://git.yoctoproject.org/meta-arm,kirkstone,HEAD,layers=meta-arm:meta-arm-toolchain
>>> -#meta-clang,https://github.com/kraj/meta-clang,kirkstone,HEAD,layers=
>>> +meta-clang,https://github.com/kraj/meta-clang,kirkstone-clang12,HEAD,layers=
>>> oe-core,https://git.openembedded.org/openembedded-core,kirkstone,HEAD,layers=meta
>>>   OECORELAYERCONF=./sample-files/bblayers.conf.sample
>>>   OECORELOCALCONF=./sample-files/local-arago64-v2.conf.sample
>>> diff --git a/configs/arago-kirkstone-next-config.txt 
>>> b/configs/arago-kirkstone-next-config.txt
>>> index dcf935d..9d173df 100644
>>> --- a/configs/arago-kirkstone-next-config.txt
>>> +++ b/configs/arago-kirkstone-next-config.txt
>>> @@ -17,7 +17,7 @@ 
>>> meta-virtualization,https://git.yoctoproject.org/meta-virtualization,kirkstone,H
>>> meta-openembedded,https://git.openembedded.org/meta-openembedded,kirkstone,HEAD,layers=meta-networking:meta-python:meta-oe:meta-gnome:meta-filesystems
>>> meta-ti,https://git.yoctoproject.org/meta-ti,kirkstone-next,HEAD,layers=meta-ti-extras:meta-ti-bsp
>>> meta-arm,https://git.yoctoproject.org/meta-arm,kirkstone,HEAD,layers=meta-arm:meta-arm-toolchain
>>> -#meta-clang,https://github.com/kraj/meta-clang,kirkstone,HEAD,layers=
>>> +meta-clang,https://github.com/kraj/meta-clang,kirkstone-clang12,HEAD,layers=
>>> oe-core,https://git.openembedded.org/openembedded-core,kirkstone,HEAD,layers=meta
>>>   OECORELAYERCONF=./sample-files/bblayers.conf.sample
>>>   OECORELOCALCONF=./sample-files/local-arago64-v2.conf.sample
>>> diff --git a/configs/arago-kirkstone-wip-config.txt 
>>> b/configs/arago-kirkstone-wip-config.txt
>>> index 9dd72ab..dfe8bd6 100644
>>> --- a/configs/arago-kirkstone-wip-config.txt
>>> +++ b/configs/arago-kirkstone-wip-config.txt
>>> @@ -9,7 +9,7 @@ 
>>> meta-virtualization,https://git.yoctoproject.org/meta-virtualization,kirkstone,H
>>> meta-openembedded,https://git.openembedded.org/meta-openembedded,kirkstone,HEAD,layers=meta-networking:meta-python:meta-oe:meta-gnome:meta-filesystems
>>> meta-ti,https://git.yoctoproject.org/meta-ti,kirkstone-wip,HEAD,layers=meta-ti-extras:meta-ti-bsp
>>> meta-arm,https://git.yoctoproject.org/meta-arm,kirkstone,HEAD,layers=meta-arm:meta-arm-toolchain
>>> -#meta-clang,https://github.com/kraj/meta-clang,kirkstone,HEAD,layers=
>>> +meta-clang,https://github.com/kraj/meta-clang,kirkstone-clang12,HEAD,layers=
>>> oe-core,https://git.openembedded.org/openembedded-core,kirkstone,HEAD,layers=meta
>>>   OECORELAYERCONF=./sample-files/bblayers.conf.sample
>>>   OECORELOCALCONF=./sample-files/local-arago64-v2.conf.sample
>>
>> Just a heads up, not sure if this can be picked up as is because of 
>> legacy devices having issues with meta-clang. It may not be a problem 
>> anymore but I remember that was what provoked the initial removal of 
>> meta-clang back around 9.1. Darren's running some tests.
> 
> I was going to ask if these had been addressed yet...
> 
> 
Well I guess this was exactly the reason for introducing this layer back 
in.  I'll run some builds on legacy and see what happens.  If it really 
is broken on legacy maybe this is something we fix on master and just 
drop this on kirkstone for now and just pull meta-clang layer in for the 
chromium builds on non-legacy devices.

On 2/8/2024 2:01 PM, Etheridge, Darren wrote:
> On 2/8/2024 1:40 PM, Ryan Eatmon wrote:
>>
>>
>> On 2/8/2024 1:34 PM, Randolph Sapp wrote:
>>> On 2/8/24 13:14, detheridge@ti.com wrote:
>>>> From: Darren Etheridge <detheridge@ti.com>
>>>>
>>>> Add meta-clang into the 3 kirkstone configs.  meta-clang is pinned to
>>>> the kirkstone-clang12 branch because this is what we will be using for
>>>> the chromium v111 browser build.
>>>>
>>>> We want to pull meta-clang into all kirkstone builds even without
>>>> chromium so that we find any integration problems that clang might
>>>> introduce even before we start doing the much larger chromium builds.
>>>>
>>>> Signed-off-by: Darren Etheridge <detheridge@ti.com>
>>>> ---
>>>>   configs/arago-kirkstone-config.txt      | 2 +-
>>>>   configs/arago-kirkstone-next-config.txt | 2 +-
>>>>   configs/arago-kirkstone-wip-config.txt  | 2 +-
>>>>   3 files changed, 3 insertions(+), 3 deletions(-)
>>>>
>>>> diff --git a/configs/arago-kirkstone-config.txt 
>>>> b/configs/arago-kirkstone-config.txt
>>>> index ceb8d74..43a8a0b 100644
>>>> --- a/configs/arago-kirkstone-config.txt
>>>> +++ b/configs/arago-kirkstone-config.txt
>>>> @@ -9,7 +9,7 @@ 
>>>> meta-virtualization,https://git.yoctoproject.org/meta-virtualization,kirkstone,H
>>>> meta-openembedded,https://git.openembedded.org/meta-openembedded,kirkstone,HEAD,layers=meta-networking:meta-python:meta-oe:meta-gnome:meta-filesystems
>>>> meta-ti,https://git.yoctoproject.org/meta-ti,kirkstone,HEAD,layers=meta-ti-extras:meta-ti-bsp
>>>> meta-arm,https://git.yoctoproject.org/meta-arm,kirkstone,HEAD,layers=meta-arm:meta-arm-toolchain
>>>> -#meta-clang,https://github.com/kraj/meta-clang,kirkstone,HEAD,layers=
>>>> +meta-clang,https://github.com/kraj/meta-clang,kirkstone-clang12,HEAD,layers=
>>>> oe-core,https://git.openembedded.org/openembedded-core,kirkstone,HEAD,layers=meta
>>>>   OECORELAYERCONF=./sample-files/bblayers.conf.sample
>>>>   OECORELOCALCONF=./sample-files/local-arago64-v2.conf.sample
>>>> diff --git a/configs/arago-kirkstone-next-config.txt 
>>>> b/configs/arago-kirkstone-next-config.txt
>>>> index dcf935d..9d173df 100644
>>>> --- a/configs/arago-kirkstone-next-config.txt
>>>> +++ b/configs/arago-kirkstone-next-config.txt
>>>> @@ -17,7 +17,7 @@ 
>>>> meta-virtualization,https://git.yoctoproject.org/meta-virtualization,kirkstone,H
>>>> meta-openembedded,https://git.openembedded.org/meta-openembedded,kirkstone,HEAD,layers=meta-networking:meta-python:meta-oe:meta-gnome:meta-filesystems
>>>> meta-ti,https://git.yoctoproject.org/meta-ti,kirkstone-next,HEAD,layers=meta-ti-extras:meta-ti-bsp
>>>> meta-arm,https://git.yoctoproject.org/meta-arm,kirkstone,HEAD,layers=meta-arm:meta-arm-toolchain
>>>> -#meta-clang,https://github.com/kraj/meta-clang,kirkstone,HEAD,layers=
>>>> +meta-clang,https://github.com/kraj/meta-clang,kirkstone-clang12,HEAD,layers=
>>>> oe-core,https://git.openembedded.org/openembedded-core,kirkstone,HEAD,layers=meta
>>>>   OECORELAYERCONF=./sample-files/bblayers.conf.sample
>>>>   OECORELOCALCONF=./sample-files/local-arago64-v2.conf.sample
>>>> diff --git a/configs/arago-kirkstone-wip-config.txt 
>>>> b/configs/arago-kirkstone-wip-config.txt
>>>> index 9dd72ab..dfe8bd6 100644
>>>> --- a/configs/arago-kirkstone-wip-config.txt
>>>> +++ b/configs/arago-kirkstone-wip-config.txt
>>>> @@ -9,7 +9,7 @@ 
>>>> meta-virtualization,https://git.yoctoproject.org/meta-virtualization,kirkstone,H
>>>> meta-openembedded,https://git.openembedded.org/meta-openembedded,kirkstone,HEAD,layers=meta-networking:meta-python:meta-oe:meta-gnome:meta-filesystems
>>>> meta-ti,https://git.yoctoproject.org/meta-ti,kirkstone-wip,HEAD,layers=meta-ti-extras:meta-ti-bsp
>>>> meta-arm,https://git.yoctoproject.org/meta-arm,kirkstone,HEAD,layers=meta-arm:meta-arm-toolchain
>>>> -#meta-clang,https://github.com/kraj/meta-clang,kirkstone,HEAD,layers=
>>>> +meta-clang,https://github.com/kraj/meta-clang,kirkstone-clang12,HEAD,layers=
>>>> oe-core,https://git.openembedded.org/openembedded-core,kirkstone,HEAD,layers=meta
>>>>   OECORELAYERCONF=./sample-files/bblayers.conf.sample
>>>>   OECORELOCALCONF=./sample-files/local-arago64-v2.conf.sample
>>>
>>> Just a heads up, not sure if this can be picked up as is because of 
>>> legacy devices having issues with meta-clang. It may not be a problem 
>>> anymore but I remember that was what provoked the initial removal of 
>>> meta-clang back around 9.1. Darren's running some tests.
>>
>> I was going to ask if these had been addressed yet...
>>
>>
> Well I guess this was exactly the reason for introducing this layer back 
> in.  I'll run some builds on legacy and see what happens.  If it really 
> is broken on legacy maybe this is something we fix on master and just 
> drop this on kirkstone for now and just pull meta-clang layer in for the 
> chromium builds on non-legacy devices.

We do not have a way to selectively pull in different layers based on 
platform.  All of the platforms are built with the same config.  So we 
either need to fix the legacy code that is not working correctly with 
clang.  Or we need to drop the legacy platforms.

On 09/02/24 01:37, Ryan Eatmon via lists.yoctoproject.org wrote:
> On 2/8/2024 2: 01 PM, Etheridge, Darren wrote: > On 2/8/2024 1: 40 PM, 
> Ryan Eatmon wrote: >> >> >> On 2/8/2024 1: 34 PM, Randolph Sapp wrote: 
> >>> On 2/8/24 13: 14, detheridge@ ti. com wrote: >>>> From: Darren
> ZjQcmQRYFpfptBannerStart
> This message was sent from outside of Texas Instruments.
> Do not click links or open attachments unless you recognize the source 
> of this email and know the content is safe.
> ZjQcmQRYFpfptBannerEnd
> On 2/8/2024 2:01 PM, Etheridge, Darren wrote:
> > On 2/8/2024 1:40 PM, Ryan Eatmon wrote:
> >>
> >>
> >> On 2/8/2024 1:34 PM, Randolph Sapp wrote:
> >>> On 2/8/24 13:14, detheridge@ti.com wrote:
> >>>> From: Darren Etheridge <detheridge@ti.com>
> >>>>
> >>>> Add meta-clang into the 3 kirkstone configs.  meta-clang is pinned to
> >>>> the kirkstone-clang12 branch because this is what we will be using for
> >>>> the chromium v111 browser build.
> >>>>
> >>>> We want to pull meta-clang into all kirkstone builds even without
> >>>> chromium so that we find any integration problems that clang might
> >>>> introduce even before we start doing the much larger chromium builds.
> >>>>
> >>>> Signed-off-by: Darren Etheridge <detheridge@ti.com>
> >>>> ---
> >>>>   configs/arago-kirkstone-config.txt      | 2 +-
> >>>>   configs/arago-kirkstone-next-config.txt | 2 +-
> >>>>   configs/arago-kirkstone-wip-config.txt  | 2 +-
> >>>>   3 files changed, 3 insertions(+), 3 deletions(-)
> >>>>
> >>>> diff --git a/configs/arago-kirkstone-config.txt 
> >>>> b/configs/arago-kirkstone-config.txt
> >>>> index ceb8d74..43a8a0b 100644
> >>>> --- a/configs/arago-kirkstone-config.txt
> >>>> +++ b/configs/arago-kirkstone-config.txt
> >>>> @@ -9,7 +9,7 @@ 
> >>>> meta-virtualization,https://urldefense.com/v3/__https://git.yoctoproject.org/meta-virtualization,kirkstone,H__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbD6XtpQ4A$
> >>>> meta-openembedded,https://urldefense.com/v3/__https://git.openembedded.org/meta-openembedded,kirkstone,HEAD,layers=meta-networking:meta-python:meta-oe:meta-gnome:meta-filesystems__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbBzMLTqzQ$
> >>>> meta-ti,https://urldefense.com/v3/__https://git.yoctoproject.org/meta-ti,kirkstone,HEAD,layers=meta-ti-extras:meta-ti-bsp__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbBm1vewiA$
> >>>> meta-arm,https://urldefense.com/v3/__https://git.yoctoproject.org/meta-arm,kirkstone,HEAD,layers=meta-arm:meta-arm-toolchain__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbCq1af67Q$
> >>>> -#meta-clang,https://urldefense.com/v3/__https://github.com/kraj/meta-clang,kirkstone,HEAD,layers=__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbAMXmWGaA$
> >>>> +meta-clang,https://urldefense.com/v3/__https://github.com/kraj/meta-clang,kirkstone-clang12,HEAD,layers=__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbCxgy6Ieg$
> >>>> oe-core,https://urldefense.com/v3/__https://git.openembedded.org/openembedded-core,kirkstone,HEAD,layers=meta__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbD3Rv3BOg$
> >>>>   OECORELAYERCONF=./sample-files/bblayers.conf.sample
> >>>>   OECORELOCALCONF=./sample-files/local-arago64-v2.conf.sample
> >>>> diff --git a/configs/arago-kirkstone-next-config.txt 
> >>>> b/configs/arago-kirkstone-next-config.txt
> >>>> index dcf935d..9d173df 100644
> >>>> --- a/configs/arago-kirkstone-next-config.txt
> >>>> +++ b/configs/arago-kirkstone-next-config.txt
> >>>> @@ -17,7 +17,7 @@ 
> >>>> meta-virtualization,https://urldefense.com/v3/__https://git.yoctoproject.org/meta-virtualization,kirkstone,H__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbD6XtpQ4A$
> >>>> meta-openembedded,https://urldefense.com/v3/__https://git.openembedded.org/meta-openembedded,kirkstone,HEAD,layers=meta-networking:meta-python:meta-oe:meta-gnome:meta-filesystems__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbBzMLTqzQ$
> >>>> meta-ti,https://urldefense.com/v3/__https://git.yoctoproject.org/meta-ti,kirkstone-next,HEAD,layers=meta-ti-extras:meta-ti-bsp__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbAMufQiNg$
> >>>> meta-arm,https://urldefense.com/v3/__https://git.yoctoproject.org/meta-arm,kirkstone,HEAD,layers=meta-arm:meta-arm-toolchain__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbCq1af67Q$
> >>>> -#meta-clang,https://urldefense.com/v3/__https://github.com/kraj/meta-clang,kirkstone,HEAD,layers=__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbAMXmWGaA$
> >>>> +meta-clang,https://urldefense.com/v3/__https://github.com/kraj/meta-clang,kirkstone-clang12,HEAD,layers=__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbCxgy6Ieg$
> >>>> oe-core,https://urldefense.com/v3/__https://git.openembedded.org/openembedded-core,kirkstone,HEAD,layers=meta__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbD3Rv3BOg$
> >>>>   OECORELAYERCONF=./sample-files/bblayers.conf.sample
> >>>>   OECORELOCALCONF=./sample-files/local-arago64-v2.conf.sample
> >>>> diff --git a/configs/arago-kirkstone-wip-config.txt 
> >>>> b/configs/arago-kirkstone-wip-config.txt
> >>>> index 9dd72ab..dfe8bd6 100644
> >>>> --- a/configs/arago-kirkstone-wip-config.txt
> >>>> +++ b/configs/arago-kirkstone-wip-config.txt
> >>>> @@ -9,7 +9,7 @@ 
> >>>> meta-virtualization,https://urldefense.com/v3/__https://git.yoctoproject.org/meta-virtualization,kirkstone,H__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbD6XtpQ4A$
> >>>> meta-openembedded,https://urldefense.com/v3/__https://git.openembedded.org/meta-openembedded,kirkstone,HEAD,layers=meta-networking:meta-python:meta-oe:meta-gnome:meta-filesystems__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbBzMLTqzQ$
> >>>> meta-ti,https://urldefense.com/v3/__https://git.yoctoproject.org/meta-ti,kirkstone-wip,HEAD,layers=meta-ti-extras:meta-ti-bsp__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbAQQJrVpA$
> >>>> meta-arm,https://urldefense.com/v3/__https://git.yoctoproject.org/meta-arm,kirkstone,HEAD,layers=meta-arm:meta-arm-toolchain__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbCq1af67Q$
> >>>> -#meta-clang,https://urldefense.com/v3/__https://github.com/kraj/meta-clang,kirkstone,HEAD,layers=__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbAMXmWGaA$
> >>>> +meta-clang,https://urldefense.com/v3/__https://github.com/kraj/meta-clang,kirkstone-clang12,HEAD,layers=__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbCxgy6Ieg$
> >>>> oe-core,https://urldefense.com/v3/__https://git.openembedded.org/openembedded-core,kirkstone,HEAD,layers=meta__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbD3Rv3BOg$
> >>>>   OECORELAYERCONF=./sample-files/bblayers.conf.sample
> >>>>   OECORELOCALCONF=./sample-files/local-arago64-v2.conf.sample
> >>>
> >>> Just a heads up, not sure if this can be picked up as is because of 
> >>> legacy devices having issues with meta-clang. It may not be a problem 
> >>> anymore but I remember that was what provoked the initial removal of 
> >>> meta-clang back around 9.1. Darren's running some tests.
> >>
> >> I was going to ask if these had been addressed yet...
> >>
> >>
> > Well I guess this was exactly the reason for introducing this layer back 
> > in.  I'll run some builds on legacy and see what happens.  If it really 
> > is broken on legacy maybe this is something we fix on master and just 
> > drop this on kirkstone for now and just pull meta-clang layer in for the 
> > chromium builds on non-legacy devices.
>
> We do not have a way to selectively pull in different layers based on
> platform.  All of the platforms are built with the same config.  So we
> either need to fix the legacy code that is not working correctly with
> clang.  Or we need to drop the legacy platforms.

Dropping legacy platforms isn't a solution as a refresh release for all 
legacy devices
is planned once a year by TI (atleast for SITARA legacy platforms)

Fixing the legacy code to avoid build due to meta-clang OR maintaining a 
separate config for legacy devices by dropping meta-clang in it
are the alternatives I can think of, with fixing the legacy code being 
the ideal choice.

Maybe, let's wait until Darren gets back with the build status of legacy 
platforms with meta-clang.

>
> -- 
> Ryan Eatmon                reatmon@ti.com
> -----------------------------------------
> Texas Instruments, Inc.  -  LCPD  -  MGTS
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#15143):https://urldefense.com/v3/__https://lists.yoctoproject.org/g/meta-arago/message/15143__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbDtL4lQBA$
> Mute This Topic:https://urldefense.com/v3/__https://lists.yoctoproject.org/mt/104245171/7030289__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbA4pCf2wQ$
> Group Owner: meta-arago+owner@lists.yoctoproject.org
> Unsubscribe:https://urldefense.com/v3/__https://lists.yoctoproject.org/g/meta-arago/unsub__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbDitwU5tg$  [c-shilwant@ti.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>

On 2/9/2024 4:17 AM, Chirag Shilwant wrote:
> 
> On 09/02/24 01:37, Ryan Eatmon via lists.yoctoproject.org wrote:
>> On 2/8/2024 2: 01 PM, Etheridge, Darren wrote: > On 2/8/2024 1: 40 PM, 
>> Ryan Eatmon wrote: >> >> >> On 2/8/2024 1: 34 PM, Randolph Sapp wrote: 
>> >>> On 2/8/24 13: 14, detheridge@ ti. com wrote: >>>> From: Darren
>> ZjQcmQRYFpfptBannerStart
>> This message was sent from outside of Texas Instruments.
>> Do not click links or open attachments unless you recognize the source 
>> of this email and know the content is safe.
>> ZjQcmQRYFpfptBannerEnd
>> On 2/8/2024 2:01 PM, Etheridge, Darren wrote:
>> > On 2/8/2024 1:40 PM, Ryan Eatmon wrote:
>> >>
>> >>
>> >> On 2/8/2024 1:34 PM, Randolph Sapp wrote:
>> >>> On 2/8/24 13:14, detheridge@ti.com wrote:
>> >>>> From: Darren Etheridge <detheridge@ti.com>
>> >>>>
>> >>>> Add meta-clang into the 3 kirkstone configs.  meta-clang is 
>> pinned to
>> >>>> the kirkstone-clang12 branch because this is what we will be 
>> using for
>> >>>> the chromium v111 browser build.
>> >>>>
>> >>>> We want to pull meta-clang into all kirkstone builds even without
>> >>>> chromium so that we find any integration problems that clang might
>> >>>> introduce even before we start doing the much larger chromium 
>> builds.
>> >>>>
>> >>>> Signed-off-by: Darren Etheridge <detheridge@ti.com>
>> >>>> ---
>> >>>>   configs/arago-kirkstone-config.txt      | 2 +-
>> >>>>   configs/arago-kirkstone-next-config.txt | 2 +-
>> >>>>   configs/arago-kirkstone-wip-config.txt  | 2 +-
>> >>>>   3 files changed, 3 insertions(+), 3 deletions(-)
>> >>>>
>> >>>> diff --git a/configs/arago-kirkstone-config.txt >>>> 
>> b/configs/arago-kirkstone-config.txt
>> >>>> index ceb8d74..43a8a0b 100644
>> >>>> --- a/configs/arago-kirkstone-config.txt
>> >>>> +++ b/configs/arago-kirkstone-config.txt
>> >>>> @@ -9,7 +9,7 @@ >>>> 
>> meta-virtualization,https://urldefense.com/v3/__https://git.yoctoproject.org/meta-virtualization,kirkstone,H__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbD6XtpQ4A$
>> >>>> 
>> meta-openembedded,https://urldefense.com/v3/__https://git.openembedded.org/meta-openembedded,kirkstone,HEAD,layers=meta-networking:meta-python:meta-oe:meta-gnome:meta-filesystems__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbBzMLTqzQ$
>> >>>> 
>> meta-ti,https://urldefense.com/v3/__https://git.yoctoproject.org/meta-ti,kirkstone,HEAD,layers=meta-ti-extras:meta-ti-bsp__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbBm1vewiA$
>> >>>> 
>> meta-arm,https://urldefense.com/v3/__https://git.yoctoproject.org/meta-arm,kirkstone,HEAD,layers=meta-arm:meta-arm-toolchain__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbCq1af67Q$
>> >>>> 
>> -#meta-clang,https://urldefense.com/v3/__https://github.com/kraj/meta-clang,kirkstone,HEAD,layers=__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbAMXmWGaA$
>> >>>> 
>> +meta-clang,https://urldefense.com/v3/__https://github.com/kraj/meta-clang,kirkstone-clang12,HEAD,layers=__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbCxgy6Ieg$
>> >>>> 
>> oe-core,https://urldefense.com/v3/__https://git.openembedded.org/openembedded-core,kirkstone,HEAD,layers=meta__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbD3Rv3BOg$
>> >>>>   OECORELAYERCONF=./sample-files/bblayers.conf.sample
>> >>>>   OECORELOCALCONF=./sample-files/local-arago64-v2.conf.sample
>> >>>> diff --git a/configs/arago-kirkstone-next-config.txt >>>> 
>> b/configs/arago-kirkstone-next-config.txt
>> >>>> index dcf935d..9d173df 100644
>> >>>> --- a/configs/arago-kirkstone-next-config.txt
>> >>>> +++ b/configs/arago-kirkstone-next-config.txt
>> >>>> @@ -17,7 +17,7 @@ >>>> 
>> meta-virtualization,https://urldefense.com/v3/__https://git.yoctoproject.org/meta-virtualization,kirkstone,H__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbD6XtpQ4A$
>> >>>> 
>> meta-openembedded,https://urldefense.com/v3/__https://git.openembedded.org/meta-openembedded,kirkstone,HEAD,layers=meta-networking:meta-python:meta-oe:meta-gnome:meta-filesystems__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbBzMLTqzQ$
>> >>>> 
>> meta-ti,https://urldefense.com/v3/__https://git.yoctoproject.org/meta-ti,kirkstone-next,HEAD,layers=meta-ti-extras:meta-ti-bsp__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbAMufQiNg$
>> >>>> 
>> meta-arm,https://urldefense.com/v3/__https://git.yoctoproject.org/meta-arm,kirkstone,HEAD,layers=meta-arm:meta-arm-toolchain__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbCq1af67Q$
>> >>>> 
>> -#meta-clang,https://urldefense.com/v3/__https://github.com/kraj/meta-clang,kirkstone,HEAD,layers=__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbAMXmWGaA$
>> >>>> 
>> +meta-clang,https://urldefense.com/v3/__https://github.com/kraj/meta-clang,kirkstone-clang12,HEAD,layers=__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbCxgy6Ieg$
>> >>>> 
>> oe-core,https://urldefense.com/v3/__https://git.openembedded.org/openembedded-core,kirkstone,HEAD,layers=meta__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbD3Rv3BOg$
>> >>>>   OECORELAYERCONF=./sample-files/bblayers.conf.sample
>> >>>>   OECORELOCALCONF=./sample-files/local-arago64-v2.conf.sample
>> >>>> diff --git a/configs/arago-kirkstone-wip-config.txt >>>> 
>> b/configs/arago-kirkstone-wip-config.txt
>> >>>> index 9dd72ab..dfe8bd6 100644
>> >>>> --- a/configs/arago-kirkstone-wip-config.txt
>> >>>> +++ b/configs/arago-kirkstone-wip-config.txt
>> >>>> @@ -9,7 +9,7 @@ >>>> 
>> meta-virtualization,https://urldefense.com/v3/__https://git.yoctoproject.org/meta-virtualization,kirkstone,H__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbD6XtpQ4A$
>> >>>> 
>> meta-openembedded,https://urldefense.com/v3/__https://git.openembedded.org/meta-openembedded,kirkstone,HEAD,layers=meta-networking:meta-python:meta-oe:meta-gnome:meta-filesystems__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbBzMLTqzQ$
>> >>>> 
>> meta-ti,https://urldefense.com/v3/__https://git.yoctoproject.org/meta-ti,kirkstone-wip,HEAD,layers=meta-ti-extras:meta-ti-bsp__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbAQQJrVpA$
>> >>>> 
>> meta-arm,https://urldefense.com/v3/__https://git.yoctoproject.org/meta-arm,kirkstone,HEAD,layers=meta-arm:meta-arm-toolchain__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbCq1af67Q$
>> >>>> 
>> -#meta-clang,https://urldefense.com/v3/__https://github.com/kraj/meta-clang,kirkstone,HEAD,layers=__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbAMXmWGaA$
>> >>>> 
>> +meta-clang,https://urldefense.com/v3/__https://github.com/kraj/meta-clang,kirkstone-clang12,HEAD,layers=__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbCxgy6Ieg$
>> >>>> 
>> oe-core,https://urldefense.com/v3/__https://git.openembedded.org/openembedded-core,kirkstone,HEAD,layers=meta__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbD3Rv3BOg$
>> >>>>   OECORELAYERCONF=./sample-files/bblayers.conf.sample
>> >>>>   OECORELOCALCONF=./sample-files/local-arago64-v2.conf.sample
>> >>>
>> >>> Just a heads up, not sure if this can be picked up as is because 
>> of >>> legacy devices having issues with meta-clang. It may not be a 
>> problem >>> anymore but I remember that was what provoked the initial 
>> removal of >>> meta-clang back around 9.1. Darren's running some tests.
>> >>
>> >> I was going to ask if these had been addressed yet...
>> >>
>> >>
>> > Well I guess this was exactly the reason for introducing this layer 
>> back > in.  I'll run some builds on legacy and see what happens.  If 
>> it really > is broken on legacy maybe this is something we fix on 
>> master and just > drop this on kirkstone for now and just pull 
>> meta-clang layer in for the > chromium builds on non-legacy devices.
>>
>> We do not have a way to selectively pull in different layers based on
>> platform.  All of the platforms are built with the same config.  So we
>> either need to fix the legacy code that is not working correctly with
>> clang.  Or we need to drop the legacy platforms.
> 
> Dropping legacy platforms isn't a solution as a refresh release for all 
> legacy devices
> is planned once a year by TI (atleast for SITARA legacy platforms)
> 
> Fixing the legacy code to avoid build due to meta-clang OR maintaining a 
> separate config for legacy devices by dropping meta-clang in it
> are the alternatives I can think of, with fixing the legacy code being 
> the ideal choice.
> 
> Maybe, let's wait until Darren gets back with the build status of legacy 
> platforms with meta-clang.
> 

Well, I did builds of am335x, am437x and am57x - and a build of 
am335x-rt with the meta-clang layer included.  All builds were 
successful,  I don't have the boards immediately at hand to run the 
images - but Randolph indicated this was a build problem, not a runtime 
problem.  Which based on my overnight builds seems to be gone now.


>>
>> -- 
>> Ryan Eatmon                reatmon@ti.com
>> -----------------------------------------
>> Texas Instruments, Inc.  -  LCPD  -  MGTS
>>
>>
>> -=-=-=-=-=-=-=-=-=-=-=-
>> Links: You receive all messages sent to this group.
>> View/Reply Online 
>> (#15143):https://urldefense.com/v3/__https://lists.yoctoproject.org/g/meta-arago/message/15143__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbDtL4lQBA$
>> Mute This 
>> Topic:https://urldefense.com/v3/__https://lists.yoctoproject.org/mt/104245171/7030289__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbA4pCf2wQ$
>> Group Owner: meta-arago+owner@lists.yoctoproject.org
>> Unsubscribe:https://urldefense.com/v3/__https://lists.yoctoproject.org/g/meta-arago/unsub__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbDitwU5tg$  [c-shilwant@ti.com]
>> -=-=-=-=-=-=-=-=-=-=-=-
>>
>>

On 2/9/2024 8:02 AM, Etheridge, Darren wrote:
> 
> 
> On 2/9/2024 4:17 AM, Chirag Shilwant wrote:
>>
>> On 09/02/24 01:37, Ryan Eatmon via lists.yoctoproject.org wrote:
>>> On 2/8/2024 2: 01 PM, Etheridge, Darren wrote: > On 2/8/2024 1: 40 
>>> PM, Ryan Eatmon wrote: >> >> >> On 2/8/2024 1: 34 PM, Randolph Sapp 
>>> wrote: >>> On 2/8/24 13: 14, detheridge@ ti. com wrote: >>>> From: 
>>> Darren
>>> ZjQcmQRYFpfptBannerStart
>>> This message was sent from outside of Texas Instruments.
>>> Do not click links or open attachments unless you recognize the 
>>> source of this email and know the content is safe.
>>> ZjQcmQRYFpfptBannerEnd
>>> On 2/8/2024 2:01 PM, Etheridge, Darren wrote:
>>> > On 2/8/2024 1:40 PM, Ryan Eatmon wrote:
>>> >>
>>> >>
>>> >> On 2/8/2024 1:34 PM, Randolph Sapp wrote:
>>> >>> On 2/8/24 13:14, detheridge@ti.com wrote:
>>> >>>> From: Darren Etheridge <detheridge@ti.com>
>>> >>>>
>>> >>>> Add meta-clang into the 3 kirkstone configs.  meta-clang is 
>>> pinned to
>>> >>>> the kirkstone-clang12 branch because this is what we will be 
>>> using for
>>> >>>> the chromium v111 browser build.
>>> >>>>
>>> >>>> We want to pull meta-clang into all kirkstone builds even without
>>> >>>> chromium so that we find any integration problems that clang might
>>> >>>> introduce even before we start doing the much larger chromium 
>>> builds.
>>> >>>>
>>> >>>> Signed-off-by: Darren Etheridge <detheridge@ti.com>
>>> >>>> ---
>>> >>>>   configs/arago-kirkstone-config.txt      | 2 +-
>>> >>>>   configs/arago-kirkstone-next-config.txt | 2 +-
>>> >>>>   configs/arago-kirkstone-wip-config.txt  | 2 +-
>>> >>>>   3 files changed, 3 insertions(+), 3 deletions(-)
>>> >>>>
>>> >>>> diff --git a/configs/arago-kirkstone-config.txt >>>> 
>>> b/configs/arago-kirkstone-config.txt
>>> >>>> index ceb8d74..43a8a0b 100644
>>> >>>> --- a/configs/arago-kirkstone-config.txt
>>> >>>> +++ b/configs/arago-kirkstone-config.txt
>>> >>>> @@ -9,7 +9,7 @@ >>>> 
>>> meta-virtualization,https://urldefense.com/v3/__https://git.yoctoproject.org/meta-virtualization,kirkstone,H__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbD6XtpQ4A$
>>> >>>> 
>>> meta-openembedded,https://urldefense.com/v3/__https://git.openembedded.org/meta-openembedded,kirkstone,HEAD,layers=meta-networking:meta-python:meta-oe:meta-gnome:meta-filesystems__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbBzMLTqzQ$
>>> >>>> 
>>> meta-ti,https://urldefense.com/v3/__https://git.yoctoproject.org/meta-ti,kirkstone,HEAD,layers=meta-ti-extras:meta-ti-bsp__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbBm1vewiA$
>>> >>>> 
>>> meta-arm,https://urldefense.com/v3/__https://git.yoctoproject.org/meta-arm,kirkstone,HEAD,layers=meta-arm:meta-arm-toolchain__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbCq1af67Q$
>>> >>>> 
>>> -#meta-clang,https://urldefense.com/v3/__https://github.com/kraj/meta-clang,kirkstone,HEAD,layers=__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbAMXmWGaA$
>>> >>>> 
>>> +meta-clang,https://urldefense.com/v3/__https://github.com/kraj/meta-clang,kirkstone-clang12,HEAD,layers=__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbCxgy6Ieg$
>>> >>>> 
>>> oe-core,https://urldefense.com/v3/__https://git.openembedded.org/openembedded-core,kirkstone,HEAD,layers=meta__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbD3Rv3BOg$
>>> >>>>   OECORELAYERCONF=./sample-files/bblayers.conf.sample
>>> >>>>   OECORELOCALCONF=./sample-files/local-arago64-v2.conf.sample
>>> >>>> diff --git a/configs/arago-kirkstone-next-config.txt >>>> 
>>> b/configs/arago-kirkstone-next-config.txt
>>> >>>> index dcf935d..9d173df 100644
>>> >>>> --- a/configs/arago-kirkstone-next-config.txt
>>> >>>> +++ b/configs/arago-kirkstone-next-config.txt
>>> >>>> @@ -17,7 +17,7 @@ >>>> 
>>> meta-virtualization,https://urldefense.com/v3/__https://git.yoctoproject.org/meta-virtualization,kirkstone,H__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbD6XtpQ4A$
>>> >>>> 
>>> meta-openembedded,https://urldefense.com/v3/__https://git.openembedded.org/meta-openembedded,kirkstone,HEAD,layers=meta-networking:meta-python:meta-oe:meta-gnome:meta-filesystems__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbBzMLTqzQ$
>>> >>>> 
>>> meta-ti,https://urldefense.com/v3/__https://git.yoctoproject.org/meta-ti,kirkstone-next,HEAD,layers=meta-ti-extras:meta-ti-bsp__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbAMufQiNg$
>>> >>>> 
>>> meta-arm,https://urldefense.com/v3/__https://git.yoctoproject.org/meta-arm,kirkstone,HEAD,layers=meta-arm:meta-arm-toolchain__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbCq1af67Q$
>>> >>>> 
>>> -#meta-clang,https://urldefense.com/v3/__https://github.com/kraj/meta-clang,kirkstone,HEAD,layers=__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbAMXmWGaA$
>>> >>>> 
>>> +meta-clang,https://urldefense.com/v3/__https://github.com/kraj/meta-clang,kirkstone-clang12,HEAD,layers=__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbCxgy6Ieg$
>>> >>>> 
>>> oe-core,https://urldefense.com/v3/__https://git.openembedded.org/openembedded-core,kirkstone,HEAD,layers=meta__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbD3Rv3BOg$
>>> >>>>   OECORELAYERCONF=./sample-files/bblayers.conf.sample
>>> >>>>   OECORELOCALCONF=./sample-files/local-arago64-v2.conf.sample
>>> >>>> diff --git a/configs/arago-kirkstone-wip-config.txt >>>> 
>>> b/configs/arago-kirkstone-wip-config.txt
>>> >>>> index 9dd72ab..dfe8bd6 100644
>>> >>>> --- a/configs/arago-kirkstone-wip-config.txt
>>> >>>> +++ b/configs/arago-kirkstone-wip-config.txt
>>> >>>> @@ -9,7 +9,7 @@ >>>> 
>>> meta-virtualization,https://urldefense.com/v3/__https://git.yoctoproject.org/meta-virtualization,kirkstone,H__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbD6XtpQ4A$
>>> >>>> 
>>> meta-openembedded,https://urldefense.com/v3/__https://git.openembedded.org/meta-openembedded,kirkstone,HEAD,layers=meta-networking:meta-python:meta-oe:meta-gnome:meta-filesystems__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbBzMLTqzQ$
>>> >>>> 
>>> meta-ti,https://urldefense.com/v3/__https://git.yoctoproject.org/meta-ti,kirkstone-wip,HEAD,layers=meta-ti-extras:meta-ti-bsp__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbAQQJrVpA$
>>> >>>> 
>>> meta-arm,https://urldefense.com/v3/__https://git.yoctoproject.org/meta-arm,kirkstone,HEAD,layers=meta-arm:meta-arm-toolchain__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbCq1af67Q$
>>> >>>> 
>>> -#meta-clang,https://urldefense.com/v3/__https://github.com/kraj/meta-clang,kirkstone,HEAD,layers=__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbAMXmWGaA$
>>> >>>> 
>>> +meta-clang,https://urldefense.com/v3/__https://github.com/kraj/meta-clang,kirkstone-clang12,HEAD,layers=__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbCxgy6Ieg$
>>> >>>> 
>>> oe-core,https://urldefense.com/v3/__https://git.openembedded.org/openembedded-core,kirkstone,HEAD,layers=meta__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbD3Rv3BOg$
>>> >>>>   OECORELAYERCONF=./sample-files/bblayers.conf.sample
>>> >>>>   OECORELOCALCONF=./sample-files/local-arago64-v2.conf.sample
>>> >>>
>>> >>> Just a heads up, not sure if this can be picked up as is because 
>>> of >>> legacy devices having issues with meta-clang. It may not be a 
>>> problem >>> anymore but I remember that was what provoked the initial 
>>> removal of >>> meta-clang back around 9.1. Darren's running some tests.
>>> >>
>>> >> I was going to ask if these had been addressed yet...
>>> >>
>>> >>
>>> > Well I guess this was exactly the reason for introducing this layer 
>>> back > in.  I'll run some builds on legacy and see what happens.  If 
>>> it really > is broken on legacy maybe this is something we fix on 
>>> master and just > drop this on kirkstone for now and just pull 
>>> meta-clang layer in for the > chromium builds on non-legacy devices.
>>>
>>> We do not have a way to selectively pull in different layers based on
>>> platform.  All of the platforms are built with the same config.  So we
>>> either need to fix the legacy code that is not working correctly with
>>> clang.  Or we need to drop the legacy platforms.
>>
>> Dropping legacy platforms isn't a solution as a refresh release for 
>> all legacy devices
>> is planned once a year by TI (atleast for SITARA legacy platforms)
>>
>> Fixing the legacy code to avoid build due to meta-clang OR maintaining 
>> a separate config for legacy devices by dropping meta-clang in it
>> are the alternatives I can think of, with fixing the legacy code being 
>> the ideal choice.
>>
>> Maybe, let's wait until Darren gets back with the build status of 
>> legacy platforms with meta-clang.
>>
> 
> Well, I did builds of am335x, am437x and am57x - and a build of 
> am335x-rt with the meta-clang layer included.  All builds were 
> successful,  I don't have the boards immediately at hand to run the 
> images - but Randolph indicated this was a build problem, not a runtime 
> problem.  Which based on my overnight builds seems to be gone now.

It was a runtime problem...  The tests failed because something became 
incredibly slower with the clang build.  It's been a while and I can't 
remember what it was...

I guess if we need to we can turn clang back on and start debugging the 
issue from there again.


> 
>>>
>>> -- 
>>> Ryan Eatmon                reatmon@ti.com
>>> -----------------------------------------
>>> Texas Instruments, Inc.  -  LCPD  -  MGTS
>>>
>>>
>>> -=-=-=-=-=-=-=-=-=-=-=-
>>> Links: You receive all messages sent to this group.
>>> View/Reply Online 
>>> (#15143):https://urldefense.com/v3/__https://lists.yoctoproject.org/g/meta-arago/message/15143__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbDtL4lQBA$
>>> Mute This 
>>> Topic:https://urldefense.com/v3/__https://lists.yoctoproject.org/mt/104245171/7030289__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbA4pCf2wQ$
>>> Group Owner: meta-arago+owner@lists.yoctoproject.org
>>> Unsubscribe:https://urldefense.com/v3/__https://lists.yoctoproject.org/g/meta-arago/unsub__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbDitwU5tg$  [c-shilwant@ti.com]
>>> -=-=-=-=-=-=-=-=-=-=-=-
>>>
>>>

On 2/9/2024 9:56 AM, Ryan Eatmon wrote:
> 
> On 2/9/2024 8:02 AM, Etheridge, Darren wrote:
>>
>>
>> On 2/9/2024 4:17 AM, Chirag Shilwant wrote:
>>>
>>> On 09/02/24 01:37, Ryan Eatmon via lists.yoctoproject.org wrote:
>>>> On 2/8/2024 2: 01 PM, Etheridge, Darren wrote: > On 2/8/2024 1: 40 
>>>> PM, Ryan Eatmon wrote: >> >> >> On 2/8/2024 1: 34 PM, Randolph Sapp 
>>>> wrote: >>> On 2/8/24 13: 14, detheridge@ ti. com wrote: >>>> From: 
>>>> Darren
>>>> ZjQcmQRYFpfptBannerStart
>>>> This message was sent from outside of Texas Instruments.
>>>> Do not click links or open attachments unless you recognize the 
>>>> source of this email and know the content is safe.
>>>> ZjQcmQRYFpfptBannerEnd
>>>> On 2/8/2024 2:01 PM, Etheridge, Darren wrote:
>>>> > On 2/8/2024 1:40 PM, Ryan Eatmon wrote:
>>>> >>
>>>> >>
>>>> >> On 2/8/2024 1:34 PM, Randolph Sapp wrote:
>>>> >>> On 2/8/24 13:14, detheridge@ti.com wrote:
>>>> >>>> From: Darren Etheridge <detheridge@ti.com>
>>>> >>>>
>>>> >>>> Add meta-clang into the 3 kirkstone configs.  meta-clang is 
>>>> pinned to
>>>> >>>> the kirkstone-clang12 branch because this is what we will be 
>>>> using for
>>>> >>>> the chromium v111 browser build.
>>>> >>>>
>>>> >>>> We want to pull meta-clang into all kirkstone builds even without
>>>> >>>> chromium so that we find any integration problems that clang might
>>>> >>>> introduce even before we start doing the much larger chromium 
>>>> builds.
>>>> >>>>
>>>> >>>> Signed-off-by: Darren Etheridge <detheridge@ti.com>
>>>> >>>> ---
>>>> >>>>   configs/arago-kirkstone-config.txt      | 2 +-
>>>> >>>>   configs/arago-kirkstone-next-config.txt | 2 +-
>>>> >>>>   configs/arago-kirkstone-wip-config.txt  | 2 +-
>>>> >>>>   3 files changed, 3 insertions(+), 3 deletions(-)
>>>> >>>>
>>>> >>>> diff --git a/configs/arago-kirkstone-config.txt >>>> 
>>>> b/configs/arago-kirkstone-config.txt
>>>> >>>> index ceb8d74..43a8a0b 100644
>>>> >>>> --- a/configs/arago-kirkstone-config.txt
>>>> >>>> +++ b/configs/arago-kirkstone-config.txt
>>>> >>>> @@ -9,7 +9,7 @@ >>>> 
>>>> meta-virtualization,https://urldefense.com/v3/__https://git.yoctoproject.org/meta-virtualization,kirkstone,H__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbD6XtpQ4A$
>>>> >>>> 
>>>> meta-openembedded,https://urldefense.com/v3/__https://git.openembedded.org/meta-openembedded,kirkstone,HEAD,layers=meta-networking:meta-python:meta-oe:meta-gnome:meta-filesystems__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbBzMLTqzQ$
>>>> >>>> 
>>>> meta-ti,https://urldefense.com/v3/__https://git.yoctoproject.org/meta-ti,kirkstone,HEAD,layers=meta-ti-extras:meta-ti-bsp__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbBm1vewiA$
>>>> >>>> 
>>>> meta-arm,https://urldefense.com/v3/__https://git.yoctoproject.org/meta-arm,kirkstone,HEAD,layers=meta-arm:meta-arm-toolchain__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbCq1af67Q$
>>>> >>>> 
>>>> -#meta-clang,https://urldefense.com/v3/__https://github.com/kraj/meta-clang,kirkstone,HEAD,layers=__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbAMXmWGaA$
>>>> >>>> 
>>>> +meta-clang,https://urldefense.com/v3/__https://github.com/kraj/meta-clang,kirkstone-clang12,HEAD,layers=__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbCxgy6Ieg$
>>>> >>>> 
>>>> oe-core,https://urldefense.com/v3/__https://git.openembedded.org/openembedded-core,kirkstone,HEAD,layers=meta__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbD3Rv3BOg$
>>>> >>>>   OECORELAYERCONF=./sample-files/bblayers.conf.sample
>>>> >>>>   OECORELOCALCONF=./sample-files/local-arago64-v2.conf.sample
>>>> >>>> diff --git a/configs/arago-kirkstone-next-config.txt >>>> 
>>>> b/configs/arago-kirkstone-next-config.txt
>>>> >>>> index dcf935d..9d173df 100644
>>>> >>>> --- a/configs/arago-kirkstone-next-config.txt
>>>> >>>> +++ b/configs/arago-kirkstone-next-config.txt
>>>> >>>> @@ -17,7 +17,7 @@ >>>> 
>>>> meta-virtualization,https://urldefense.com/v3/__https://git.yoctoproject.org/meta-virtualization,kirkstone,H__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbD6XtpQ4A$
>>>> >>>> 
>>>> meta-openembedded,https://urldefense.com/v3/__https://git.openembedded.org/meta-openembedded,kirkstone,HEAD,layers=meta-networking:meta-python:meta-oe:meta-gnome:meta-filesystems__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbBzMLTqzQ$
>>>> >>>> 
>>>> meta-ti,https://urldefense.com/v3/__https://git.yoctoproject.org/meta-ti,kirkstone-next,HEAD,layers=meta-ti-extras:meta-ti-bsp__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbAMufQiNg$
>>>> >>>> 
>>>> meta-arm,https://urldefense.com/v3/__https://git.yoctoproject.org/meta-arm,kirkstone,HEAD,layers=meta-arm:meta-arm-toolchain__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbCq1af67Q$
>>>> >>>> 
>>>> -#meta-clang,https://urldefense.com/v3/__https://github.com/kraj/meta-clang,kirkstone,HEAD,layers=__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbAMXmWGaA$
>>>> >>>> 
>>>> +meta-clang,https://urldefense.com/v3/__https://github.com/kraj/meta-clang,kirkstone-clang12,HEAD,layers=__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbCxgy6Ieg$
>>>> >>>> 
>>>> oe-core,https://urldefense.com/v3/__https://git.openembedded.org/openembedded-core,kirkstone,HEAD,layers=meta__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbD3Rv3BOg$
>>>> >>>>   OECORELAYERCONF=./sample-files/bblayers.conf.sample
>>>> >>>>   OECORELOCALCONF=./sample-files/local-arago64-v2.conf.sample
>>>> >>>> diff --git a/configs/arago-kirkstone-wip-config.txt >>>> 
>>>> b/configs/arago-kirkstone-wip-config.txt
>>>> >>>> index 9dd72ab..dfe8bd6 100644
>>>> >>>> --- a/configs/arago-kirkstone-wip-config.txt
>>>> >>>> +++ b/configs/arago-kirkstone-wip-config.txt
>>>> >>>> @@ -9,7 +9,7 @@ >>>> 
>>>> meta-virtualization,https://urldefense.com/v3/__https://git.yoctoproject.org/meta-virtualization,kirkstone,H__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbD6XtpQ4A$
>>>> >>>> 
>>>> meta-openembedded,https://urldefense.com/v3/__https://git.openembedded.org/meta-openembedded,kirkstone,HEAD,layers=meta-networking:meta-python:meta-oe:meta-gnome:meta-filesystems__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbBzMLTqzQ$
>>>> >>>> 
>>>> meta-ti,https://urldefense.com/v3/__https://git.yoctoproject.org/meta-ti,kirkstone-wip,HEAD,layers=meta-ti-extras:meta-ti-bsp__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbAQQJrVpA$
>>>> >>>> 
>>>> meta-arm,https://urldefense.com/v3/__https://git.yoctoproject.org/meta-arm,kirkstone,HEAD,layers=meta-arm:meta-arm-toolchain__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbCq1af67Q$
>>>> >>>> 
>>>> -#meta-clang,https://urldefense.com/v3/__https://github.com/kraj/meta-clang,kirkstone,HEAD,layers=__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbAMXmWGaA$
>>>> >>>> 
>>>> +meta-clang,https://urldefense.com/v3/__https://github.com/kraj/meta-clang,kirkstone-clang12,HEAD,layers=__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbCxgy6Ieg$
>>>> >>>> 
>>>> oe-core,https://urldefense.com/v3/__https://git.openembedded.org/openembedded-core,kirkstone,HEAD,layers=meta__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbD3Rv3BOg$
>>>> >>>>   OECORELAYERCONF=./sample-files/bblayers.conf.sample
>>>> >>>>   OECORELOCALCONF=./sample-files/local-arago64-v2.conf.sample
>>>> >>>
>>>> >>> Just a heads up, not sure if this can be picked up as is because 
>>>> of >>> legacy devices having issues with meta-clang. It may not be a 
>>>> problem >>> anymore but I remember that was what provoked the 
>>>> initial removal of >>> meta-clang back around 9.1. Darren's running 
>>>> some tests.
>>>> >>
>>>> >> I was going to ask if these had been addressed yet...
>>>> >>
>>>> >>
>>>> > Well I guess this was exactly the reason for introducing this 
>>>> layer back > in.  I'll run some builds on legacy and see what 
>>>> happens.  If it really > is broken on legacy maybe this is something 
>>>> we fix on master and just > drop this on kirkstone for now and just 
>>>> pull meta-clang layer in for the > chromium builds on non-legacy 
>>>> devices.
>>>>
>>>> We do not have a way to selectively pull in different layers based on
>>>> platform.  All of the platforms are built with the same config.  So we
>>>> either need to fix the legacy code that is not working correctly with
>>>> clang.  Or we need to drop the legacy platforms.
>>>
>>> Dropping legacy platforms isn't a solution as a refresh release for 
>>> all legacy devices
>>> is planned once a year by TI (atleast for SITARA legacy platforms)
>>>
>>> Fixing the legacy code to avoid build due to meta-clang OR 
>>> maintaining a separate config for legacy devices by dropping 
>>> meta-clang in it
>>> are the alternatives I can think of, with fixing the legacy code 
>>> being the ideal choice.
>>>
>>> Maybe, let's wait until Darren gets back with the build status of 
>>> legacy platforms with meta-clang.
>>>
>>
>> Well, I did builds of am335x, am437x and am57x - and a build of 
>> am335x-rt with the meta-clang layer included.  All builds were 
>> successful,  I don't have the boards immediately at hand to run the 
>> images - but Randolph indicated this was a build problem, not a 
>> runtime problem.  Which based on my overnight builds seems to be gone 
>> now.
> 
> It was a runtime problem...  The tests failed because something became 
> incredibly slower with the clang build.  It's been a while and I can't 
> remember what it was...
> 
> I guess if we need to we can turn clang back on and start debugging the 
> issue from there again.
> 

Sounds like that is what we need to do.


> 
>>
>>>>
>>>> -- 
>>>> Ryan Eatmon                reatmon@ti.com
>>>> -----------------------------------------
>>>> Texas Instruments, Inc.  -  LCPD  -  MGTS
>>>>
>>>>
>>>> -=-=-=-=-=-=-=-=-=-=-=-
>>>> Links: You receive all messages sent to this group.
>>>> View/Reply Online 
>>>> (#15143):https://urldefense.com/v3/__https://lists.yoctoproject.org/g/meta-arago/message/15143__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbDtL4lQBA$
>>>> Mute This 
>>>> Topic:https://urldefense.com/v3/__https://lists.yoctoproject.org/mt/104245171/7030289__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbA4pCf2wQ$
>>>> Group Owner: meta-arago+owner@lists.yoctoproject.org
>>>> Unsubscribe:https://urldefense.com/v3/__https://lists.yoctoproject.org/g/meta-arago/unsub__;!!G3vK!T-4ApZ-eTAnXM7YmK4gmtSSGBxuhgwAcpVEP9umR0-KUKAHuXRzuVl-uWTjTuqtWRxIKm1-NhEWk-O4dSbfBAtmdwbDitwU5tg$  [c-shilwant@ti.com]
>>>> -=-=-=-=-=-=-=-=-=-=-=-
>>>>
>>>>
>