Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Christian Stewart via buildroot <buildroot@buildroot.org>
Cc: Anisse Astier <anisse@astier.eu>,
	Christian Stewart <christian@aperture.us>,
	"Yann E . MORIN" <yann.morin.1998@free.fr>
Subject: Re: [Buildroot] [PATCH v1 1/1] package/go: bump to version 1.21.0
Date: Wed, 30 Aug 2023 23:58:31 +0200	[thread overview]
Message-ID: <20230830235831.53b3e903@windsurf> (raw)
In-Reply-To: <20230829222230.1884427-1-christian@aperture.us>

On Tue, 29 Aug 2023 15:22:30 -0700
Christian Stewart via buildroot <buildroot@buildroot.org> wrote:

> Go 1.21.0 is a major release of Go.
> 
> https://go.dev/doc/devel/release#go1.21.0
> 
> Set GOTOOLCHAIN=local to disable the new toolchain download feature. This
> feature, introduced in Go 1.21.x, will automatically download pre-built compiler
> binaries from Google for the toolchain version specified in go.mod. We do not
> want this in Buildroot as we build from source instead: set GOTOOLCHAIN=local to
> disable the feature and use the locally built toolchain.
> 
> https://go.dev/doc/toolchain
> 
> Signed-off-by: Christian Stewart <christian@aperture.us>
> ---
>  package/go/go.hash | 2 +-
>  package/go/go.mk   | 3 ++-
>  2 files changed, 3 insertions(+), 2 deletions(-)

Applied to next, 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

      reply	other threads:[~2023-08-30 21:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-29 22:22 [Buildroot] [PATCH v1 1/1] package/go: bump to version 1.21.0 Christian Stewart via buildroot
2023-08-30 21:58 ` Thomas Petazzoni via buildroot [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=20230830235831.53b3e903@windsurf \
    --to=buildroot@buildroot.org \
    --cc=anisse@astier.eu \
    --cc=christian@aperture.us \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=yann.morin.1998@free.fr \
    /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