-
Notifications
You must be signed in to change notification settings - Fork 17.7k
New issue
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? Sign in to your account
cmd/cgo: invalid pkg-config package name: --static #23944
Labels
Comments
CC: @ianlancetaylor |
I just pulled down master and it seems to have solved the issue. Any guesstimate on a point release containing this fix? Thanks! |
No ETA, sorry. |
mikioh
changed the title
invalid pkg-config package name: --static
cmd/cgo: invalid pkg-config package name: --static
Feb 21, 2018
I have the same problem with go 1.9.4 linux/amd64. Is this going to be fixed in 1.9 as well? |
It was fixed in 1.9.5 in c1bf152 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (
go version
)?go version go1.10 darwin/amd64
Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?Irrevelent
What did you do?
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 myGOPATH
. So, to make that work I have a script that does something like:This worked fine in the past (<= 1.9.3), but now I'm getting:
If I do a
go get github.com/flier/gohs
and then do ago 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. I saw that https://go-review.googlesource.com/#/c/94896/ addresses some issue related to--static
and was used to close #23875. It isn't clear to me if that change would affect this use case or not. Let me know if I can provide any extra information to help produce a test case.What did you expect to see?
The package successfully build
What did you see instead?
The error
invalid pkg-config package name: --static
The text was updated successfully, but these errors were encountered: