GNU Arm Embedded Toolchain recipe

GNU Arm Embedded Toolchain recipe

[Jon Mason]

There are a number of recipes floating around inside and outside of
Arm to support the GNU Arm Embedded Toolchain.  Specifically,
https://git.yoctoproject.org/cgit/cgit.cgi/meta-ti/tree/recipes-ti/devtools/gcc-arm-none-eabi-native_4.9.2015q3.bb
https://git.yoctoproject.org/cgit/cgit.cgi/meta-ti/tree/recipes-ti/devtools/gcc-arm-none-eabi_7-2018-q2-update.bb
https://git.yoctoproject.org/cgit/cgit.cgi/meta-rockchip/tree/recipes-devtools/gcc-arm-none-eabi/gcc-arm-none-eabi-native_9-2019-q4-major.bb

After looking at the website
(https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-rm/downloads),
the latest version is 9-2019-q4-major.  Given this, I think the best
approach is to simply import the recipe from meta-rockchip into
meta-arm-toolchains and use that is the starting point.

Assuming everyone is fine with this, are their any other legacy
versions that are needed by other layers?

Thanks,
Jon

Re: [meta-arm] GNU Arm Embedded Toolchain recipe

[Khasim Mohammed]

Hi Jon,

---
From: meta-arm@lists.yoctoproject.org <meta-arm@lists.yoctoproject.org> on behalf of Jon Mason via lists.yoctoproject.org <jdmason=kudzu.us@lists.yoctoproject.org>

Sent: Thursday, May 14, 2020 8:10 AM

To: meta-arm@lists.yoctoproject.org <meta-arm@lists.yoctoproject.org>

Cc: Joshua Watt <JPEWhacker@gmail.com>; Denys Dmytriyenko <denys@ti.com>; Diego Sueiro <Diego.Sueiro@arm.com>

Subject: [meta-arm] GNU Arm Embedded Toolchain recipe




> There are a number of recipes floating around inside and outside of

> Arm to support the GNU Arm Embedded Toolchain.  Specifically,

> https://git.yoctoproject.org/cgit/cgit.cgi/meta-ti/tree/recipes-ti/devtools/gcc-arm-none-eabi-native_4.9.2015q3.bb

> https://git.yoctoproject.org/cgit/cgit.cgi/meta-ti/tree/recipes-ti/devtools/gcc-arm-none-eabi_7-2018-q2-update.bb

> https://git.yoctoproject.org/cgit/cgit.cgi/meta-rockchip/tree/recipes-devtools/gcc-arm-none-eabi/gcc-arm-none-eabi-native_9-2019-q4-major.bb

> After looking at the website

> (https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-rm/downloads),

> the latest version is 9-2019-q4-major.  Given this, I think the best

> approach is to simply import the recipe from meta-rockchip into

> meta-arm-toolchains and use that is the starting point.

Few software components are validated for a particular version of GCC though ideally it should work for latest but we won't get support from the respective teams if we switch to a different toolchain. So we need a mechanism to pull different versions of toolchains.

Having said that, I think it is better we start improvising meta-arm-toolchain with all required recipes instead of importing from meta-rockchip. In future we prefer meta-rockchip imports meta-arm-toolchain recipes.

> Assuming everyone is fine with this, are their any other legacy

> versions that are needed by other layers?

As mentioned above SCP 2.6 needs a particular version : https://developer.arm.com/-/media/Files/downloads/gnu-rm/7-2018q2/gcc-arm-none-eabi-7-2018-q2-update-linux.tar.bz2

> Thanks,
> Jon

Regards,
Khasim
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

Re: [meta-arm] GNU Arm Embedded Toolchain recipe

[Bertrand Marquis]

[-- Attachment #1: Type: text/plain, Size: 3315 bytes --]

Hi,

On 14 May 2020, at 09:04, Khasim Mohammed via lists.yoctoproject.org<http://lists.yoctoproject.org> <khasim.mohammed=arm.com@lists.yoctoproject.org<mailto:khasim.mohammed=arm.com@lists.yoctoproject.org>> wrote:

Hi Jon,

---
From: meta-arm@lists.yoctoproject.org<mailto:meta-arm@lists.yoctoproject.org> <meta-arm@lists.yoctoproject.org<mailto:meta-arm@lists.yoctoproject.org>> on behalf of Jon Mason via lists.yoctoproject.org<http://lists.yoctoproject.org/> <jdmason=kudzu.us@lists.yoctoproject.org<mailto:jdmason=kudzu.us@lists.yoctoproject.org>>

Sent: Thursday, May 14, 2020 8:10 AM

To: meta-arm@lists.yoctoproject.org<mailto:meta-arm@lists.yoctoproject.org> <meta-arm@lists.yoctoproject.org<mailto:meta-arm@lists.yoctoproject.org>>

Cc: Joshua Watt <JPEWhacker@gmail.com<mailto:JPEWhacker@gmail.com>>; Denys Dmytriyenko <denys@ti.com<mailto:denys@ti.com>>; Diego Sueiro <Diego.Sueiro@arm.com<mailto:Diego.Sueiro@arm.com>>

Subject: [meta-arm] GNU Arm Embedded Toolchain recipe




There are a number of recipes floating around inside and outside of

Arm to support the GNU Arm Embedded Toolchain.  Specifically,

https://git.yoctoproject.org/cgit/cgit.cgi/meta-ti/tree/recipes-ti/devtools/gcc-arm-none-eabi-native_4.9.2015q3.bb

https://git.yoctoproject.org/cgit/cgit.cgi/meta-ti/tree/recipes-ti/devtools/gcc-arm-none-eabi_7-2018-q2-update.bb

https://git.yoctoproject.org/cgit/cgit.cgi/meta-rockchip/tree/recipes-devtools/gcc-arm-none-eabi/gcc-arm-none-eabi-native_9-2019-q4-major.bb

After looking at the website

(https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-rm/downloads),

the latest version is 9-2019-q4-major.  Given this, I think the best

approach is to simply import the recipe from meta-rockchip into

meta-arm-toolchains and use that is the starting point.

Few software components are validated for a particular version of GCC though ideally it should work for latest but we won't get support from the respective teams if we switch to a different toolchain. So we need a mechanism to pull different versions of toolchains.

Having said that, I think it is better we start improvising meta-arm-toolchain with all required recipes instead of importing from meta-rockchip. In future we prefer meta-rockchip imports meta-arm-toolchain recipes.

Assuming everyone is fine with this, are their any other legacy

versions that are needed by other layers?

As mentioned above SCP 2.6 needs a particular version : https://developer.arm.com/-/media/Files/downloads/gnu-rm/7-2018q2/gcc-arm-none-eabi-7-2018-q2-update-linux.tar.bz2

Is this a recommendation or is there a major incompatibility with an other version ?

Did you try with the latest version ?

It might well be that they tested with only one version and that’s why they recommend it but we cannot afford to have one particular compiler per package.

Bertrand


Thanks,
Jon

Regards,
Khasim
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.



[-- Attachment #2: Type: text/html, Size: 35689 bytes --]

Re: [meta-arm] GNU Arm Embedded Toolchain recipe

[Khasim Mohammed]

[-- Attachment #1: Type: text/plain, Size: 4425 bytes --]

Hi,

________________________________
From: Bertrand Marquis <Bertrand.Marquis@arm.com>
Sent: Thursday, May 14, 2020 1:37 PM
To: Khasim Mohammed <Khasim.Mohammed@arm.com>; meta-arm@lists.yoctoproject.org <meta-arm@lists.yoctoproject.org>
Cc: jdmason@kudzu.us <jdmason@kudzu.us>; Joshua Watt <JPEWhacker@gmail.com>; Denys Dmytriyenko <denys@ti.com>; Diego Sueiro <Diego.Sueiro@arm.com>; nd <nd@arm.com>
Subject: Re: [meta-arm] GNU Arm Embedded Toolchain recipe

Hi,

On 14 May 2020, at 09:04, Khasim Mohammed via lists.yoctoproject.org<http://lists.yoctoproject.org> <khasim.mohammed=arm.com@lists.yoctoproject.org<mailto:khasim.mohammed=arm.com@lists.yoctoproject.org>> wrote:

Hi Jon,

---
From: meta-arm@lists.yoctoproject.org<mailto:meta-arm@lists.yoctoproject.org> <meta-arm@lists.yoctoproject.org<mailto:meta-arm@lists.yoctoproject.org>> on behalf of Jon Mason via lists.yoctoproject.org<http://lists.yoctoproject.org/> <jdmason=kudzu.us@lists.yoctoproject.org<mailto:jdmason=kudzu.us@lists.yoctoproject.org>>

Sent: Thursday, May 14, 2020 8:10 AM

To: meta-arm@lists.yoctoproject.org<mailto:meta-arm@lists.yoctoproject.org> <meta-arm@lists.yoctoproject.org<mailto:meta-arm@lists.yoctoproject.org>>

Cc: Joshua Watt <JPEWhacker@gmail.com<mailto:JPEWhacker@gmail.com>>; Denys Dmytriyenko <denys@ti.com<mailto:denys@ti.com>>; Diego Sueiro <Diego.Sueiro@arm.com<mailto:Diego.Sueiro@arm.com>>

Subject: [meta-arm] GNU Arm Embedded Toolchain recipe




There are a number of recipes floating around inside and outside of

Arm to support the GNU Arm Embedded Toolchain.  Specifically,

https://git.yoctoproject.org/cgit/cgit.cgi/meta-ti/tree/recipes-ti/devtools/gcc-arm-none-eabi-native_4.9.2015q3.bb

https://git.yoctoproject.org/cgit/cgit.cgi/meta-ti/tree/recipes-ti/devtools/gcc-arm-none-eabi_7-2018-q2-update.bb

https://git.yoctoproject.org/cgit/cgit.cgi/meta-rockchip/tree/recipes-devtools/gcc-arm-none-eabi/gcc-arm-none-eabi-native_9-2019-q4-major.bb

After looking at the website

(https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-rm/downloads),

the latest version is 9-2019-q4-major.  Given this, I think the best

approach is to simply import the recipe from meta-rockchip into

meta-arm-toolchains and use that is the starting point.

Few software components are validated for a particular version of GCC though ideally it should work for latest but we won't get support from the respective teams if we switch to a different toolchain. So we need a mechanism to pull different versions of toolchains.

Having said that, I think it is better we start improvising meta-arm-toolchain with all required recipes instead of importing from meta-rockchip. In future we prefer meta-rockchip imports meta-arm-toolchain recipes.

Assuming everyone is fine with this, are their any other legacy

versions that are needed by other layers?

As mentioned above SCP 2.6 needs a particular version : https://developer.arm.com/-/media/Files/downloads/gnu-rm/7-2018q2/gcc-arm-none-eabi-7-2018-q2-update-linux.tar.bz2

> Is this a recommendation or is there a major incompatibility with an other version ?
Actually on their portal they show 2019-q4 as supported version.

> Did you try with the latest version ?
Not yet,

> It might well be that they tested with only one version and that’s why they recommend it but we cannot afford to have one particular compiler per package.
I agree, I was only concerned about the validation, if we use the tested toolchain then I don't have to do thorough validation if I use different toolchain then validation will be on me :(

Let me give this a try

Bertrand

Regards,
Khasim


Thanks,
Jon

Regards,
Khasim
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.


IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

[-- Attachment #2: Type: text/html, Size: 31302 bytes --]