cmd/go: go test complains about missing gcc (even if no tests exist, and only for certain imports)

[jhinrichsen]

Please answer these questions before submitting your issue. Thanks!

What version of Go are you using (go version)?

go version go1.11 linux/amd64

Does this issue reproduce with the latest release?

Yes, 1.11 is the latest release.

What operating system and processor architecture are you using (go env)?

GOARCH="amd64"
GOBIN=""
GOCACHE="/home/jot/.cache/go-build"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/jot/go"
GOPROXY=""
GORACE=""
GOROOT="/home/jot/bin/go"
GOTMPDIR=""
GOTOOLDIR="/home/jot/bin/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build025056307=/tmp/go-build -gno-record-gcc-switches"

What did you do?

Create an empty directory, and copy a single main.go file.

Working: https://play.golang.org/p/sctz4PAGjf1
Breaking: https://play.golang.org/p/aZu1NZdtXel

Run go test

What did you expect to see?

The working main.go file shows the expected message [no test files].

What did you see instead?

The breaking main.go shows the error message

# runtime/cgo exec: "gcc": executable file not found in $PATH

Go 1.10.4 shows the correct message. Setting CGO_ENABLED="0" also leads to the correct message.

Using debian 9 (stretch) in a Windows Linux Subsystem.

[ianlancetaylor]

Most likely a dup of #26988 and/or #27285.

[palsivertsen]

Shouldn't this be part of Go1.11.1? Or are there any workarounds?

Running a CI pipeline is problematic when go test fails on the simplest of files:

package foo
import  _ "net/http"

[ianlancetaylor]

This problem has been reported several times in several different bugs. We should probably try to concentrate on one issue. CC @bcmills

[bcmills]

I'm starting with #27285 because it's easy to reproduce and leads to similar symptoms. I plan to recheck this issue once that one is resolved, in case the underlying cause is the same for both.

[bcmills]

Pretty sure this one in particular is a dup of #26988.

[jkomyno]

Setting the environment variable CGO_ENABLED to 0 fixed it for me.

If you use docker, insert the following before your RUN go test or RUN go build operation:

ENV CGO_ENABLED 0

[cespedes]

Pretty sure this one in particular is a dup of #26988.

It's not :(

With go version go1.12.7 linux/amd64, "go build" does not need gcc, but "go test" does.

Having a directory with just one file, "foo.go", with just the lines:

package foo
import _ "net"

results in:

$ go test
# runtime/cgo
exec: "gcc": executable file not found in $PATH

[blafasel42]

ENV CGO_ENABLED 0 solved it for me

[wojnosystems]

Setting the environment variable CGO_ENABLED to 0 fixed it for me.

If you use docker, insert the following before your RUN go test or RUN go build operation:

ENV CGO_ENABLED 0

This also worked for me, but I did:

RUN CGO_ENABLED=0 go test -run="" /tmp/build/pkg/*

To avoid setting an environment variable.

Thanks jkomyno