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/go: whitelist @includedir@ and @libdir@ in CGO flags #24505
Comments
Do you actually have directories named The problem with whitelisting this kind of option is that Looking at github.com/abh/geoip, it uses |
Hi, Hmm, I didn't know
I hope that is helpful. I am using CentOS 6.9. |
Unless you actually have a directory literally named |
Yeah, I don't have a directory called I'm going to close this as I think it doesn't affect anyone else -- from what I can tell, this isn't a CentOS problem but an issue with my company's RPM server. Thank you very much for helping me to debug this so far. |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes.
What operating system and processor architecture are you using (
go env
)?What did you do?
Running
go get
on the source code below will yield an error. Here is a minimal program that exhibits this behavior:I have to get, build, and run by putting this prefix in front, or by using export:
What did you expect to see?
Go get, build, and run working the same way it did in 1.9.
As is described in the InvalidFlag section on the wiki, would it be possible to have these whitelisted in Go?
What did you see instead?
The text was updated successfully, but these errors were encountered: