From ca829f14e0b0d44719229c1be1b3cbf2cee39b4e Mon Sep 17 00:00:00 2001 From: Jose Quaresma Date: Thu, 7 Mar 2024 02:06:59 -0800 Subject: go.bbclass: set GOPROXY The GOPROXY is already correctly defined on the native sys root and this can be checked using the bitbake devshell: | $ go env GOPROXY | https://proxy.golang.org,direct The go_do_compile task calls the compiler directly so the GOPROXY env is not seen because it's not defined in the shell. Defining it explicitly solves this problem and was to avoid setting it in the recipes itself. (From OE-Core rev: e0919a3f7bc26b1ea9fb57740de4a9a3b9253f26) Signed-off-by: Jose Quaresma Signed-off-by: Richard Purdie --- meta/classes-recipe/go.bbclass | 1 + 1 file changed, 1 insertion(+) diff --git a/meta/classes-recipe/go.bbclass b/meta/classes-recipe/go.bbclass index 39bfaa5156..cc3564c36a 100644 --- a/meta/classes-recipe/go.bbclass +++ b/meta/classes-recipe/go.bbclass @@ -78,6 +78,7 @@ GO_INSTALL_FILTEROUT ?= "${GO_IMPORT}/vendor/" B = "${WORKDIR}/build" export GOPATH = "${B}" export GOENV = "off" +export GOPROXY ??= "https://proxy.golang.org,direct" export GOTMPDIR ?= "${WORKDIR}/build-tmp" GOTMPDIR[vardepvalue] = "" -- cgit v1.2.3-54-g00ecf