From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] toolchain: update AArch32/AArch64 toolchain to 8-2-2019.01
Date: Mon, 28 Jan 2019 15:59:51 +0100 [thread overview]
Message-ID: <20190128155951.6eb96b67@windsurf> (raw)
In-Reply-To: <20190128143507.GA31160@guppy>
Hello,
On Mon, 28 Jan 2019 15:35:07 +0100
Joakim Bech <joakim.bech@linaro.org> wrote:
> > I don't see how this can be sufficient to update the toolchain version.
> > Surely the .mk and .hash files need to be changed as well.
> >
> Chapter 17.3 and 17.4 is about this in the documentation, right?
>
> For hash files, are you referring to these:
>
> $ find -name "*.hash" | grep gcc
> ./package/gcc/gcc-initial/gcc-initial.hash
> ./package/gcc/gcc.hash
> ./package/gcc/gcc-final/gcc-final.hash
These are all the same files, thanks to symlinks. But anyway, these
files are not relevant, since they are for the "internal toolchain"
backend (i.e when Buildroot builds a toolchain) and not the external
toolchain backend.
In your case, I don't see how the version bump can work if you don't
change:
toolchain/toolchain-external/toolchain-external-arm-aarch64/toolchain-external-arm-aarch64.mk
toolchain/toolchain-external/toolchain-external-arm-aarch64/toolchain-external-arm-aarch64.hash
toolchain/toolchain-external/toolchain-external-arm-arm/toolchain-external-arm-arm.mk
toolchain/toolchain-external/toolchain-external-arm-arm/toolchain-external-arm-arm.hash
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-01-28 14:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190128133500.7515-1-joakim.bech@linaro.org>
2019-01-28 14:02 ` [Buildroot] [PATCH 1/1] toolchain: update AArch32/AArch64 toolchain to 8-2-2019.01 Joakim Bech
2019-01-28 14:08 ` Thomas Petazzoni
2019-01-28 14:35 ` Joakim Bech
2019-01-28 14:59 ` Thomas Petazzoni [this message]
2019-01-28 16:41 ` Joakim Bech
2019-01-28 17:05 ` [Buildroot] [PATCH v2 1/1] toolchain: update AArch32/AArch64 toolchains " Joakim Bech
2019-01-28 22:22 ` Arnout Vandecappelle
2019-01-29 10:26 ` Joakim Bech
2019-01-29 11:27 ` Arnout Vandecappelle
2019-01-29 11:34 ` Arnout Vandecappelle
2019-01-29 12:00 ` Joakim Bech
2019-02-04 10:08 ` Peter Korsgaard
2019-02-04 12:42 ` Arnout Vandecappelle
2019-02-04 16:10 ` Peter Korsgaard
2019-01-29 11:55 ` Joakim Bech
2019-01-29 11:40 ` Baruch Siach
2019-01-29 11:50 ` Joakim Bech
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=20190128155951.6eb96b67@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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