Add gcc-arm-none-eabi

[nmosim]

Checklist

• Title of this PR is meaningful: e.g. "Adding my_nifty_package", not "updated meta.yaml".
• License file is packaged (see here for an example).
• Source is from official source.
• Package does not vendor other packages. (If a package uses the source of another package, they should be separate packages or the licenses of all packages need to be packaged).
• If static libraries are linked in, the license of the static library is packaged.
• Package does not ship static libraries. If static libraries are needed, follow CFEP-18.
• Build number is 0.
• A tarball (url) rather than a repo (e.g. git_url) is used in your recipe (see here for more details).
• GitHub users listed in the maintainer section have posted a comment confirming they are willing to be listed there.
• When in trouble, please check our knowledge base documentation before pinging a team.

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/gcc-arm-none-eabi/meta.yaml) and found some lint.

Here's what I've got...

For recipes/gcc-arm-none-eabi/meta.yaml:

• The recipe could do with some maintainers listed in the extra/recipe-maintainers section.

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipes/gcc-arm-none-eabi/meta.yaml) and found it was in an excellent condition.

[nmosim]

@conda-forge/help-c-cpp Ready for review!

[nmosim]

@conda-forge-admin, please ping team

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-webservice.

I was asked to ping @conda-forge/staged-recipes and so here I am doing that.

[github-actions]

To help direct your pull request to the best reviewers, please mention a topic-specifc team if your recipe matches any of the following: conda-forge/help-c-cpp, conda-forge/help-cdts, conda-forge/help-go, conda-forge/help-java, conda-forge/help-julia, conda-forge/help-nodejs, conda-forge/help-perl, conda-forge/help-python, conda-forge/help-python-c, conda-forge/help-r, conda-forge/help-ruby,or conda-forge/help-rust. Thanks!

[xhochy]

I don't think this should be added but you should rather use the toolchains we already provide in conda-forge.

[nmosim]

I don't think this should be added but you should rather use the toolchains we already provide in conda-forge.

Which toolchain did you mean exactly? This toolchain is used for embedded processors (e.g. ARM Cortex) and it is not available on conda-forge yet.

[carterbox]

I think what @xhochy means is that we already have compiler packages which can target the aarch64 architecture. Compiler packages are special because they require a specific package structure and other changes in order for the rest of our infrastructure to be able to use the compiler. It might be best if you appear at one of our meetings or start a discussion on our Zulip.

https://conda-forge.org/community/getting-in-touch/

[github-actions]

Hi! This is the staged-recipes linter and your PR looks excellent! 🚀