From: "Changqing Li" <changqing.li@windriver.com>
To: Naveen Saini <naveen.kumar.saini@intel.com>,
Khem Raj <raj.khem@gmail.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>,
Richard Purdie <richard.purdie@linuxfoundation.org>
Subject: Re: [OE-core] [PATCH v2 3/3] go-helloworld: Turn into a go module enabled build
Date: Mon, 22 Mar 2021 11:22:51 +0800 [thread overview]
Message-ID: <b307aaa6-2228-1aec-3d2f-41f33fbe694f@windriver.com> (raw)
In-Reply-To: <5baa9e0336304fa281deaf975e3f1191@intel.com>
[-- Attachment #1: Type: text/plain, Size: 2825 bytes --]
On 3/2/21 5:49 PM, Naveen Saini wrote:
> [Please note: This e-mail is from an EXTERNAL e-mail address]
>
> This is now failing when you are behind a proxy because it's trying to fetch those modules during do_compile().
> https://github.com/golang/example/commit/bcf50bfd7dcd8020c90965747d857ae42802e0c5
>
> Error log:
>
> | ERROR: Execution of '~/build/tmp/work/corei7-64-poky-linux/go-helloworld/0.1-r0/temp/run.do_compile.26031' failed with exit code 1:
> | go: golang.org/x/tools@v0.0.0-20210112183307-1e6ecd4bf1b0: Get "https://proxy.golang.org/golang.org/x/tools/@v/v0.0.0-20210112183307-1e6ecd4bf1b0.mod": dial tcp 216.58.196.49:443: i/o timeout
> | go: golang.org/x/tools@v0.0.0-20210112183307-1e6ecd4bf1b0: Get "https://proxy.golang.org/golang.org/x/tools/@v/v0.0.0-20210112183307-1e6ecd4bf1b0.mod": dial tcp 216.58.196.49:443: i/o timeout
>
> Regards,
> Naveen
I send a patch to disable the module-aware mode for this recipe, as
module-aware mode blocks offline build
and condition when proxy.golang.org is not accssible.
But disable module-aware mode is just a temporary workaround, now go is
1.16, from go1.17, GOPATH mode will be dropped,
GO111MODULE will be ignored. Maybe, the final solution should be
making bitbake's fetcher support offline build with
go module-aware mode.
>
>> -----Original Message-----
>> From: openembedded-core@lists.openembedded.org <openembedded-
>> core@lists.openembedded.org> On Behalf Of Khem Raj
>> Sent: Wednesday, February 24, 2021 12:13 PM
>> To: openembedded-core@lists.openembedded.org
>> Cc: Khem Raj <raj.khem@gmail.com>
>> Subject: [OE-core] [PATCH v2 3/3] go-helloworld: Turn into a go module
>> enabled build
>>
>> Signed-off-by: Khem Raj <raj.khem@gmail.com>
>> ---
>> meta/recipes-extended/go-examples/go-helloworld_0.1.bb | 5 +++--
>> 1 file changed, 3 insertions(+), 2 deletions(-)
>>
>> diff --git a/meta/recipes-extended/go-examples/go-helloworld_0.1.bb
>> b/meta/recipes-extended/go-examples/go-helloworld_0.1.bb
>> index ab70ea98a3..d3f7525dc9 100644
>> --- a/meta/recipes-extended/go-examples/go-helloworld_0.1.bb
>> +++ b/meta/recipes-extended/go-examples/go-helloworld_0.1.bb
>> @@ -6,13 +6,14 @@ LICENSE = "MIT"
>> LIC_FILES_CHKSUM =
>> "file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b
>> 4f302"
>>
>> SRC_URI = "git://${GO_IMPORT}"
>> -SRCREV = "46695d81d1fae905a270fb7db8a4d11a334562fe"
>> +SRCREV = "bcf50bfd7dcd8020c90965747d857ae42802e0c5"
>> UPSTREAM_CHECK_COMMITS = "1"
>>
>> GO_IMPORT = "github.com/golang/example"
>> GO_INSTALL = "${GO_IMPORT}/hello"
>> +GO_WORKDIR = "${GO_INSTALL}"
>>
>> -inherit go
>> +inherit go-mod
>>
>> # This is just to make clear where this example is
>> do_install_append() {
>> --
>> 2.30.1
>
>
>
[-- Attachment #2: Type: text/html, Size: 4816 bytes --]
prev parent reply other threads:[~2021-03-22 3:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 4:13 [PATCH v2 1/3] go: Upgrade compiler to 1.16 major release Khem Raj
2021-02-24 4:13 ` [PATCH v2 2/3] go: Enable CGO and pie buildmode on rv64 Khem Raj
2021-02-24 4:13 ` [PATCH v2 3/3] go-helloworld: Turn into a go module enabled build Khem Raj
2021-03-02 9:49 ` [OE-core] " Naveen Saini
2021-03-02 12:46 ` Richard Purdie
2021-03-22 3:22 ` Changqing Li [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=b307aaa6-2228-1aec-3d2f-41f33fbe694f@windriver.com \
--to=changqing.li@windriver.com \
--cc=naveen.kumar.saini@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--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