From: Angelo Compagnucci <angelo.compagnucci@gmail.com>
To: buildroot@buildroot.org
Cc: Charles Hardin <ckhardin@gmail.com>,
Christian Stewart <christian@aperture.us>
Subject: Re: [Buildroot] [1/1] package/go-native: add a new download only package for go compilers
Date: Fri, 20 Nov 2026 23:13:34 +0100 [thread overview]
Message-ID: <20261120221334.639761-1-angelo.compagnucci@gmail.com> (raw)
In-Reply-To: <20230707185106.98208-1-ckhardin@gmail.com>
Hi Charles,
On 07/07/23 20:51, Charles Hardin wrote:
> The go-native is mainly for the aarch64 support since that was
> added after the go-bootstrap written in C was dropped. So, to
> get a cross compiler for go a host/native compiler needs to be
> available to generate the setup for the needed target.
I think this patch can be dropped: Buildroot now does the same thing.
Since commit 7b2a164b7460 ("package/go/go-bin: new host-go provider"),
"host go (pre-built)" downloads the official Go binaries from go.dev,
arm64 included.
On an aarch64 build machine, the Go bootstrap from source is not
available (stage 1 only supports x86, x86_64 and arm), so Buildroot
selects the pre-built compiler by itself.
Not Applicable: https://patchwork.buildroot.org/project/buildroot/patch/20230707185106.98208-1-ckhardin@gmail.com/
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-11-20 22:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-07 18:51 [Buildroot] [PATCH 1/1] package/go-native: add a new download only package for go compilers Charles Hardin
2023-07-07 19:04 ` Christian Stewart via buildroot
2023-07-07 19:07 ` Christian Stewart via buildroot
2023-07-07 20:05 ` Charles Hardin
2023-07-07 20:19 ` Christian Stewart via buildroot
2026-11-20 22:13 ` Angelo Compagnucci [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=20261120221334.639761-1-angelo.compagnucci@gmail.com \
--to=angelo.compagnucci@gmail.com \
--cc=buildroot@buildroot.org \
--cc=christian@aperture.us \
--cc=ckhardin@gmail.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