Am 23.06.20 um 21:56 schrieb Khem Raj:
On 6/23/20 11:35 AM, Stefan Herbrechtsmeier wrote:
Am 23.06.20 um 20:16 schrieb Khem Raj:
On Tue, Jun 23, 2020 at 9:47 AM Otavio Salvador <otavio.salva...@ossystems.com.br <mailto:otavio.salva...@ossystems.com.br>> wrote:

    Hello Stefan,

    Em ter., 23 de jun. de 2020 às 13:37, Stefan Herbrechtsmeier
    <ste...@herbrechtsmeier.net <mailto:ste...@herbrechtsmeier.net>>
    escreveu:
     > because of the changes to the 'GO111MODULE' variable in go-dep and
     > glide, I wonder if Go is ready for use. I would have expected the
     > variable GO111MODULE to be set to 'off' within the go.bbclass
    because go
     > could bypass the fetch task unobserved otherwise.

    Is there any known issue?

    For me, with those fixes, it is working fine.


Yes it’s working ok with go-module for me but not sure of go-dep has regresse

What is the expected behavior of go-module and go-dep? Does they work without network connection after a bitbake -c fetch?

I think so. Its perhaps after first build unless you clean the build tree.

The go-mod.bbclass download data from the internet during do_compile. If you cut the internet connection after a do_fetch the do_compile failed:

| DEBUG: Executing shell function do_compile
| go: github.com/nats-io/jwt@v0.3.2: Get "https://proxy.golang.org/github.com/nats-io/jwt/@v/v0.3.2.mod": dial tcp: lookup proxy.golang.org on 127.0.0.53:53: server misbehaving | go: github.com/nats-io/jwt@v0.3.2: Get "https://proxy.golang.org/github.com/nats-io/jwt/@v/v0.3.2.mod": dial tcp: lookup proxy.golang.org on 127.0.0.53:53: server misbehaving



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#139899): 
https://lists.openembedded.org/g/openembedded-core/message/139899
Mute This Topic: https://lists.openembedded.org/mt/75063635/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to