This is with the final released version of 1.10? A fix for that went in quite late in the process.

Yup I just downloaded it from golang.org a few minutes before the report

I can't recreate the problem. Can you show a complete test case? Thanks.

After some checking I found out what's wrong. I'm setting --static in multiple files.
While exec is only allowing the first arg in the list to contain --

That's a loop, though.

Assuming this is still a problem for you, I'd still like to see a test case. Thanks.

Test case is just any 2+ files with --static in the pkgconfig args.

main.go

package main

/*
	#cgo pkg-config: --static SDL2
*/
import "C"

func main() {

}

foo.go

package main

/*
	#cgo pkg-config: --static SDL2
*/
import "C"

func foo() {

}

Change https://golang.org/cl/94896 mentions this issue: cmd/go: permit pkg-config flags in any argument position

Hmm...I'm having a similar problem (same error), but maybe it is different enough to be worth describing. I have a project that relies on https://github.com/flier/gohs (golang wrapper around an Intel developed C library called hyperscan). My usage requires that I build the tool that relies on gohs inside of a local directory not related to my GOPATH. So, to make that work I have a script that does something like:

gopath=$(cd "$installdir" && pwd)
cd "$builddir"
GOPATH=$gopath go build

This worked fine in the past, but now I'm getting:

go build github.com/github/myproject/vendor/github.com/flier/gohs/hyperscan: invalid pkg-config package name: --static

If I do a go get github.com/flier/gohs and then do a go build github.com/flier/gohs/hyperscan it builds fine. But, if I try to do the build in a "non-standard" directory I get the whitelist error. Would you imagine the fix in https://go-review.googlesource.com/#/c/94896/ would fix what I'm seeing? Let me know if I can provide any extra information to help produce a test case.

Hmm...I'm having a similar problem (same error), but maybe it is different enough to be worth describing.

If it's different enough to be worth describing, it's worth being in its open bug (or at least on a bug that's not closed and thus not tracked).

@bradfitz - Will do. I only added it hear since it wasn't clear to me if my issue was obviously addressed by the patch that closed this issue already.

Reopening for 1.10.1.

CL 94896 OK for Go 1.10.1

Change https://golang.org/cl/102779 mentions this issue: [release-branch.go1.10] cmd/go: permit pkg-config flags in any argument position

Change https://golang.org/cl/103155 mentions this issue: [release-branch.go1.9] cmd/go: permit pkg-config flags in any argument position