You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Building packages using pkg-config and using pkg-config flags like --static
where the environment variable PKG_CONFIG_PATH is unset to force a error.
What did you expect to see?
# pkg-config --cflags --static sdl2
Package sdl2 was not found in the pkg-config search path.
Perhaps you should add the directory containing `sdl2.pc'
to the PKG_CONFIG_PATH environment variable
No package 'sdl2' found
pkg-config: exit status 1
What did you see instead?
# pkg-config --cflags --staticsdl2
Package sdl2 was not found in the pkg-config search path.
Perhaps you should add the directory containing `sdl2.pc'
to the PKG_CONFIG_PATH environment variable
No package 'sdl2' found
pkg-config: exit status 1
There is a missing space between --static and sdl2, as far as I can tell this affects both the --cflags and --libs errors.
I am willing to send a PR however I'm not sure if this needs a test as it seems pretty trivial and completely harmless (only affects the error message).
Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (
go version
)?go version go1.10.2 linux/amd64
Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?Irrevent
What did you do?
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
Building packages using pkg-config and using pkg-config flags like
--static
where the environment variable
PKG_CONFIG_PATH
is unset to force a error.What did you expect to see?
What did you see instead?
There is a missing space between
--static
andsdl2
, as far as I can tell this affects both the--cflags
and--libs
errors.go/src/cmd/go/internal/work/exec.go
Line 990 in f7c767e
go/src/cmd/go/internal/work/exec.go
Line 1005 in f7c767e
I am willing to send a PR however I'm not sure if this needs a test as it seems pretty trivial and completely harmless (only affects the error message).
cc @ianlancetaylor
The text was updated successfully, but these errors were encountered: