From: "Khem Raj" <raj.khem@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: Otavio Salvador <otavio.salvador@gmail.com>,
Otavio Salvador <otavio@ossystems.com.br>,
Richard Purdie <richard.purdie@linuxfoundation.org>
Subject: [dunfell][PATCH 3/4] go-dep: Avoid use of 'go mod' support
Date: Mon, 22 Jun 2020 13:02:29 -0700 [thread overview]
Message-ID: <20200622200230.54899-3-raj.khem@gmail.com> (raw)
In-Reply-To: <20200622200230.54899-1-raj.khem@gmail.com>
From: Otavio Salvador <otavio.salvador@gmail.com>
dep utility must not use 'go mod' support, so we explicitly disable it.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---
meta/recipes-devtools/go/go-dep_0.5.4.bb | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/meta/recipes-devtools/go/go-dep_0.5.4.bb b/meta/recipes-devtools/go/go-dep_0.5.4.bb
index 615cb289e5..496224a5cf 100644
--- a/meta/recipes-devtools/go/go-dep_0.5.4.bb
+++ b/meta/recipes-devtools/go/go-dep_0.5.4.bb
@@ -13,6 +13,10 @@ SRCREV = "1f7c19e5f52f49ffb9f956f64c010be14683468b"
inherit go
+# New Go versions has Go modules support enabled by default and cause the Glide
+# tool build to fail.
+export GO111MODULE = "off"
+
GO_INSTALL = "${GO_IMPORT}/cmd/dep"
RDEPENDS_${PN}-dev += "bash"
--
2.27.0
next prev parent reply other threads:[~2020-06-22 20:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-22 20:02 [dunfell][PATCH 1/4] go-mod.bbclass: Add class for `go mod` support Khem Raj
2020-06-22 20:02 ` [dunfell][PATCH 2/4] go.bbclass: Add `-trimpath` to default build flags Khem Raj
2020-06-22 20:02 ` Khem Raj [this message]
2020-06-22 20:02 ` [dunfell][PATCH 4/4] glide: Avoid use of 'go mod' support Khem Raj
2020-06-22 20:12 ` [OE-core] [dunfell][PATCH 1/4] go-mod.bbclass: Add class for `go mod` support Steve Sakoman
2020-06-22 23:08 ` Khem Raj
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=20200622200230.54899-3-raj.khem@gmail.com \
--to=raj.khem@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio.salvador@gmail.com \
--cc=otavio@ossystems.com.br \
--cc=richard.purdie@linuxfoundation.org \
/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