We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.
Already on GitHub?
to your account
$ go version
go version go1.12.9 linux/amd64
Yes, tested with latest stable version (1.12.9).
$ go env
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build945969099=/tmp/go-build -gno-record-gcc-switches"
$ cat foo.go
import _ "net"
$ go test foo.go
exec: "gcc": executable file not found in $PATH
"go build" runs without problems, but "go test" needs gcc.
AFAIK, this bug is the same as #27303, but not #26988. Both were closed, but the former is not fixed yet (at least with 1.12.9).
The text was updated successfully, but these errors were encountered:
Have the similar issue.
Based on #27303, the following works,
But is this issue really solved?
Sorry, something went wrong.
Issue does not occur probably since https://go-review.googlesource.com/c/go/+/335409/
but other changes have occur.
Error now returned for case provided ? command-line-arguments [no test files] which seems appropriate.
? command-line-arguments [no test files]
I believe this was already fixed, but Go 1.20 will fix this again by automatically disabling cgo if there is no C compiler.
No branches or pull requests