From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Tom Wambold <tom5760@gmail.com>
Cc: buildroot@buildroot.org,
Christian Stewart <christian@aperture.us>,
Thomas Perale <thomas.perale@mind.be>
Subject: Re: [Buildroot] [PATCH v2] package/go: go-bin host-go provider implies target support
Date: Sun, 18 May 2025 16:47:09 +0200 [thread overview]
Message-ID: <20250518164709.72083fe6@windsurf> (raw)
In-Reply-To: <20250518141452.4f6ea693@windsurf>
Hello,
On Sun, 18 May 2025 14:14:52 +0200
Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:
> This basically extends the thing to say: "In order to build Go packages
> for the target, we need:
>
> 1. A compiler that runs on our host: either bootstrapped, or pre-compiled (go-bin)
>
> 2. A target architecture that's supported
> "
>
> Tom, Christian, what do you think?
FYI, I tried my proposal, and it does work: I was able to build a Go
package (tinifier) for the ARM architecture, on an ARM64 host (on which
bootstrapping Go is not possible).
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-05-18 14:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-14 15:42 [Buildroot] [PATCH] package/go: go-bin host-go provider implies target support Tom Wambold
2025-03-31 15:34 ` [Buildroot] [PATCH v2] " Tom Wambold
2025-05-18 12:14 ` Thomas Petazzoni via buildroot
2025-05-18 14:47 ` Thomas Petazzoni via buildroot [this message]
2025-05-18 15:43 ` Tom Wambold
2025-05-25 7:13 ` Christian Stewart via buildroot
2025-07-19 13:12 ` Tom Wambold
2025-07-19 16:36 ` Christian Stewart via buildroot
2025-05-18 15:33 ` [Buildroot] [PATCH v3] " Tom Wambold
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=20250518164709.72083fe6@windsurf \
--to=buildroot@buildroot.org \
--cc=christian@aperture.us \
--cc=thomas.perale@mind.be \
--cc=thomas.petazzoni@bootlin.com \
--cc=tom5760@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