From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bryce Johnson <bryce@redpinelabs.com>
Cc: buildroot@buildroot.org, Suniel Mahesh <sunil@amarulasolutions.com>
Subject: Re: [Buildroot] [PATCH] package/arm-gnu-toolchain: Add $(HOSTARCH) so can be built with aarch64
Date: Tue, 22 Oct 2024 23:17:36 +0200 [thread overview]
Message-ID: <20241022231736.7e5626ef@windsurf> (raw)
In-Reply-To: <20241022210334.261117-1-bryce@redpinelabs.com>
On Tue, 22 Oct 2024 15:03:34 -0600
Bryce Johnson <bryce@redpinelabs.com> wrote:
> Was testing building with arm64 build server and failed because it
> was downloading the x86_64 version.
>
> Use $(HOSTARCH) instead so it can also downloaded
>
> Tested with building configs/ti_am62x_sk_defconfig on arm64 that it
> uses to build the 32bit R5 MCU.
>
> Signed-off-by: Bryce Johnson <bryce@redpinelabs.com>
> ---
> package/arm-gnu-toolchain/arm-gnu-toolchain.hash | 2 ++
> package/arm-gnu-toolchain/arm-gnu-toolchain.mk | 2 +-
> 2 files changed, 3 insertions(+), 1 deletion(-)
Applied to master with an improved commit log. Though I believe making
this dependency more explicit would be useful, as suggested on my
review to your v1. Thanks!
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
next prev parent reply other threads:[~2024-10-22 21:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 21:03 [Buildroot] [PATCH] package/arm-gnu-toolchain: Add $(HOSTARCH) so can be built with aarch64 Bryce Johnson
2024-10-22 21:17 ` Thomas Petazzoni via buildroot [this message]
2024-10-22 21:37 ` Bryce Johnson
2024-10-23 16:22 ` Thomas Petazzoni via buildroot
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=20241022231736.7e5626ef@windsurf \
--to=buildroot@buildroot.org \
--cc=bryce@redpinelabs.com \
--cc=sunil@amarulasolutions.com \
--cc=thomas.petazzoni@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.