go has a feature of workspaces [1]. If there is a file called go.work in your working directory on any of its parent directories that will be read and used during build. For OE where the builds shall be sandboxed this is bad as a workspace file outside of the build environment can be picked up. This commit wil disable that feature according to the instruction in [1].
This was found and introduced build failures when a file go.work was in the parent directory outside of OE build directory. [1] https://go.dev/ref/mod#workspaces Signed-off-by: Peter Bergin <[email protected]> --- 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 c323d4c9c93..b540471ba2d 100644 --- a/meta/classes-recipe/go.bbclass +++ b/meta/classes-recipe/go.bbclass @@ -24,6 +24,7 @@ export GOARCH = "${TARGET_GOARCH}" export GOOS = "${TARGET_GOOS}" export GOHOSTARCH = "${BUILD_GOARCH}" export GOHOSTOS = "${BUILD_GOOS}" +export GOWORK = "off" GOARM[export] = "0" GOARM:arm:class-target = "${TARGET_GOARM}"
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#228109): https://lists.openembedded.org/g/openembedded-core/message/228109 Mute This Topic: https://lists.openembedded.org/mt/116840331/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
