build constraints exclude all Go files in

Question

when import "golang.org/x/net/route"

it tells "build constraints exclude all Go files in go/src/golang.org/x/net/routego"

I am using VSCode editor on Windows/Linux

I searched online and didn't see a solution to the similar problem

package main

import (
    "golang.org/x/net/route"
)

{
    rib, _ := route.FetchRIB(0, route.RIBTypeRoute, 0)
    messages, err := route.ParseRIB(route.RIBTypeRoute, rib)
}

score 35 · Answer 1 · answered Aug 29 '22 at 15:44

35

I had this problem in Goland (with source code on WSL2 and Goland on win).

I was able to solve it with

go clean -modcache

Subsequent build put everything in order again.

answered Aug 29 '22 at 15:44

Andreas Gnyp

1,500
1
19
25

This solved my problem. And I understand that go does intelligence around what files to build, if you set the `GO_OS` or name a file like `xyz_.go`, which can lead to the unfortunate fact of having 0 files to build with even though there are source files in the pwd... However, I'm not sure what happened such that removing cached modules fixes this? What happened? – Ari Sweedler Nov 18 '22 at 16:28
I'm rather new to Go, so I drew from my "general experience" and speculated, after some reading here, that the cache was "mixed up". Meaning, I was installing packages using Golang AND the console. If there is some configuration going on--as you mentioned--the cache would "contradict" itself. Once again, just a thought! And I'd be very happy to amend my answer with a proper explanation, if we find something reproducible. – Andreas Gnyp Nov 19 '22 at 18:16
This got me mostly there. Running `go mod tidy` completed the task. – Virmundi Jun 16 '23 at 18:49

zangw · Answer 2 · 2022-08-04T02:58:12.227

We met the same error under Goland, and it could be solved in this way

If you want to set GOOS = linux under Mac, just add this line in the header of file // +build linux,amd64,go1.15,!cgo which means we declare that this file is for the target system that has the following requirements: Linux, the AMD64 architecture, the 1.15 Go version, and no CGO support.

Update 08/04/2022

After go 1.17. The go command now understands //go:build lines and prefers them over // +build lines. The new syntax uses boolean expressions, just like Go, and should be less error-prone. Here are some more details

// go:build (darwin && cgo) || linux
// +build darwin,cgo linux

score 7 · Answer 3 · answered Jan 09 '23 at 20:13

7

My issue was that I had a stray import "C" in my code and I was compiling with CGO_ENABLED=0. This problem was hard to find because IntelliJ collapses all the imports into one statement.

answered Jan 09 '23 at 20:13

user2233706

6,148
5
44
86

temporary enable cgo with: **env CGO_ENABLED=1 go run main** – hmmftg Jun 18 '23 at 15:56

score 4 · Answer 4 · answered Oct 12 '20 at 05:33

4

try to remove folder x in go/src/golang.org/

answered Oct 12 '20 at 05:33

RK26

373
1
5
20

score 3 · Answer 5 · answered Feb 07 '22 at 20:40

3

In my case I just by an accident replaced original code by test file, it was containing the following comments:

//go:build unittest
// +build unittest

answered Feb 07 '22 at 20:40

kvaps

2,589
1
21
20

upvoted! This seems like it would be a commonly overlooked issue. I had the inversion of this issue. I.E. my test file didn't have the build constraints indicating this is a test file - so my test file wasn't allowed to import our core test files. The complication in my case was my test file was importing a package which requires cgo to be enabled - so I wasted a bunch of time ensuring that cgo had all necessary prequisites enabled. – Tim Feb 26 '23 at 18:42

score 3 · Answer 6 · answered Apr 19 '23 at 03:35

3

I fixed the issue by simply doing Invalidate Caches under File Tab.

answered Apr 19 '23 at 03:35

fzdy1914

31
1

score 2 · Answer 7 · answered Mar 23 '23 at 13:51

2

If you have a dependency requiring cgo (which includes x/net by default), you will get this error if your system does not have a C compiler. Can be easily fixed by installing gcc.

answered Mar 23 '23 at 13:51

Lundis

371
1
2
13

1

Yeah, that's what it turned out to be for me. I was working in a new codebase (and I'm new to Go) and didn't have GCC on my box. I installed GCC and it built. The error message is misleading. – peterfelts May 12 '23 at 17:37

score 1 · Answer 8 · answered Oct 06 '22 at 11:53

1

This error seems to present itself rather ambiguously.

In my case, my project uses CGO, and this error manifests when CGO_ENABLED=0 in the environment, which is solved by unsetting this env var, or setting CGO_ENABLED=1

answered Oct 06 '22 at 11:53

DevOops

943
2
10
21

score 1 · Answer 9 · answered Nov 13 '22 at 01:21

1

In my case it appears the go get failed and the folder referenced in GOPATH was empty. Check your library folder which is complaining here.

answered Nov 13 '22 at 01:21

MousyBusiness

188
2
14

score 0 · Answer 10 · answered Jun 14 '23 at 10:16

0

In my case, after trying the go clean -modcache solution, I also had to restart Goland before it stopped complaining about the build constraints.

answered Jun 14 '23 at 10:16

Martin Meli

452
5
18

score -1 · Answer 11 · answered Oct 04 '21 at 03:02

-1

"build constraints exclude all Go files in go/src/golang.org/x/net/routego" In Intellij :

Navigate to the folder in the project explorer
Right click -> Mark folder as not excluded.

answered Oct 04 '21 at 03:02

Sheetal Kaul

3,029
2
13
6

cbg.hongminh · Answer 12 · 2021-10-20T12:21:09.237

-2

If you get error build constraints exclude all Go files in ... with go get command, please specify the path as follows

Error:

$ go get {HOST}/platform/be-photo

Success:

$ go get {HOST}/platform/be-photo/external/client

edited Oct 20 '21 at 12:21

answered Oct 20 '21 at 05:27

cbg.hongminh

1
1

build constraints exclude all Go files in

12 Answers12

Linked

Related