From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Andrey Nechypurenko <andreynech@gmail.com>
Cc: "Köry Maincent" <kory.maincent@bootlin.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] Building packages for Cortex M4
Date: Fri, 10 Dec 2021 23:10:55 +0100 [thread overview]
Message-ID: <20211210231055.550d5641@windsurf> (raw)
In-Reply-To: <CAOiXNkBvvsC2g5GR0r6fMHQRVpUGHpZHeQNQvJYOODcp5XVorg@mail.gmail.com>
Hello Andrey,
On Thu, 9 Dec 2021 18:02:27 +0100
Andrey Nechypurenko <andreynech@gmail.com> wrote:
> In the meantime, I came up with the following solution and wondered what
> would you say about it. First, I made host package which downloads and
> installs M4 toolchain from ARM site (inspired by
> https://gist.github.com/titouanc/ea0685d9cd8592deb1c49d48e33b3eee )
>
> Config.in.host:
>
> ################################################################################
> #
> # gcc-arm-none-eabi
> #
> ################################################################################
We already have a package for an ARM toolchain, in
package/arm-gnu-a-toolchain/. However, we have found that this
toolchain is targeted at Cortex-A, and while in theory it should work
for Cortex-M as well, the Cortex-M examples from ST (at least) expect
some libraries that are not in the Cortex-A toolchain provided by ARM,
but only the Cortex-M.
This is why in
https://github.com/bootlin/buildroot/commit/8635d412292eec7bb90bfabcba25a8c238aa2f93
we switch to the Cortex-M/Cortex-R toolchain for this package. But this
isn't directly suitable for upstream. More work is needed here.
> Except for a couple of small errors in the CMakeLists.txt which need yet to be
> fixed, it looks like this solution would work for me.
>
> What do you think about it?
Yes, that looks, except for the toolchain package, where we probably
want to re-use what already exists :)
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-12-10 22:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-08 16:46 [Buildroot] Building packages for Cortex M4 Andrey Nechypurenko
2021-12-09 14:10 ` Thomas Petazzoni
2021-12-09 17:02 ` Andrey Nechypurenko
2021-12-10 22:10 ` Thomas Petazzoni [this message]
2021-12-13 17:49 ` Andrey Nechypurenko
2021-12-11 8:35 ` Arnout Vandecappelle
2021-12-13 17:36 ` Andrey Nechypurenko
2021-12-13 17:52 ` Yann E. MORIN
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211210231055.550d5641@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=andreynech@gmail.com \
--cc=buildroot@buildroot.org \
--cc=kory.maincent@bootlin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox