From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Kory Maincent <kory.maincent@bootlin.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/arm-gnu-a-toolchain: bump to version 10.3-2021.07
Date: Thu, 30 Dec 2021 16:59:23 +0100 [thread overview]
Message-ID: <20211230165923.6a6be968@windsurf> (raw)
In-Reply-To: <20210908081630.3404221-1-kory.maincent@bootlin.com>
Hello Köry,
On Wed, 8 Sep 2021 10:16:30 +0200
Kory Maincent <kory.maincent@bootlin.com> wrote:
> Update to version 10.3-2021.07.
> The old version contained a nasty nano.spec. The nano.spec file was adding
> -lc_nano option but the c_nano.a library was not delivered in the
> toolchain archive.
>
> Signed-off-by: Kory Maincent <kory.maincent@bootlin.com>
> ---
> package/arm-gnu-a-toolchain/arm-gnu-a-toolchain.hash | 2 +-
> package/arm-gnu-a-toolchain/arm-gnu-a-toolchain.mk | 6 +++---
> 2 files changed, 4 insertions(+), 4 deletions(-)
So, I have applied, but with a very important change: I really bump the
gnu-a toolchain, I don't switch to the gnu-rm toolchain, which should
be added as a separate package, because it's different.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2021-12-30 15:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-08 8:16 [Buildroot] [PATCH] package/arm-gnu-a-toolchain: bump to version 10.3-2021.07 Kory Maincent
2021-09-19 12:35 ` Arnout Vandecappelle
2021-09-19 13:09 ` Thomas Petazzoni
2021-09-20 9:18 ` Arnout Vandecappelle
2021-09-20 12:01 ` Thomas Petazzoni
2021-09-20 18:52 ` Arnout Vandecappelle
2021-09-23 19:55 ` Thomas Petazzoni
2021-09-23 21:20 ` Arnout Vandecappelle
2021-11-30 10:37 ` Köry Maincent
2021-12-30 15:59 ` Thomas Petazzoni [this message]
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=20211230165923.6a6be968@windsurf \
--to=thomas.petazzoni@bootlin.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