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. Signed-off-by: Jose Quaresma <jose.quare...@foundries.io> --- 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] = "" -- 2.44.0
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#196783): https://lists.openembedded.org/g/openembedded-core/message/196783 Mute This Topic: https://lists.openembedded.org/mt/104784533/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
