From: Joakim Bech <joakim.bech@linaro.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] toolchain: update AArch32/AArch64 toolchain to 8-2-2019.01
Date: Mon, 28 Jan 2019 17:41:40 +0100 [thread overview]
Message-ID: <20190128164140.GA6634@guppy> (raw)
In-Reply-To: <20190128155951.6eb96b67@windsurf>
Hi,
On Mon, Jan 28, 2019 at 03:59:51PM +0100, Thomas Petazzoni wrote:
> In your case, I don't see how the version bump can work if you don't
> change:
>
When I'm building for OP-TEE we are pre-downloading the toolchain from the
OP-TEE makefiles and refer to that when configuring Buildroot, which explains
why this was working on my side even before making the changes you're asking
for.
> 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
>
Got it! I've made changes to those files and this time I've also tested
directly in Buildroot (without involving OP-TEE) as follows:
1) $ make qemu_aarch64_virt_defconfig
$ make menuconfig ... select external toolchain
$ make
...
2019-01-28 17:06:00 (1.11 MB/s) - ?/home/jbech/devel/optee_projects/qemu_v8/buildroot/output/build/.gcc-arm-8.2-2019.01-x86_64-aarch64-linux-gnu.tar.xz.7NG7Nw/output? saved [267998260/267998260]
gcc-arm-8.2-2019.01-x86_64-aarch64-linux-gnu.tar.xz: OK (md5: ed467a18abc7cf81d53c0cf6014b1867)
gcc-arm-8.2-2019.01-x86_64-aarch64-linux-gnu.tar.xz: OK (sha256: 6683d51b0dd61a91ab1e8e478a0a8a50ccb34d5590c84aa36697e956b16f14a1)
2) $ make qemu_arm_vexpress_defconfig
$ make menuconfig ... select external toolchain
$ make
...
2019-01-28 17:26:29 (1.11 MB/s) - ?/home/jbech/devel/optee_projects/qemu_v8/buildroot/output/build/.gcc-arm-8.2-2019.01-x86_64-arm-linux-gnueabihf.tar.xz.XkMAPN/output? saved [252108596/252108596]
gcc-arm-8.2-2019.01-x86_64-arm-linux-gnueabihf.tar.xz: OK (md5: 123887bdaa27b362f0f428dc36af5693)
gcc-arm-8.2-2019.01-x86_64-arm-linux-gnueabihf.tar.xz: OK (sha256: 6b73016fa4773a7450bac9bd80b2ca056b5d582dd966b509a17b305fc89506a9)
Which I believe looks good and what we would expect (the builds also ended
successfully). I will send v2-patch soon, thanks for the guidance!
--
Regards,
Joakim
next prev parent reply other threads:[~2019-01-28 16:41 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
2019-01-28 16:41 ` Joakim Bech [this message]
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=20190128164140.GA6634@guppy \
--to=joakim.bech@linaro.org \
--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