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? Sign in to your account
Description of the Go fix that breaks compilation: http://golang.org/issue/23672
LDFLAGS now has a whitelist in place for options it accepts, and it doesn't accept bare filenames. This breaks compilation of ui.
LDFLAGS
ui
ui/link_linux_386.go
Line 8 in 2dde2a7
There should probably be a -l added in front of the base library name, and a -L for the directory.
-l
-L
The text was updated successfully, but these errors were encountered:
I cannot make any fixes currently. What would the equivalent fix on Windows be (note that it needs to link to a .res file as well)?
Sorry, something went wrong.
Fixed by Go itself. See also golang/go#23749
No branches or pull requests
Description of the Go fix that breaks compilation: http://golang.org/issue/23672
LDFLAGS
now has a whitelist in place for options it accepts, and it doesn't accept bare filenames. This breaks compilation ofui
.ui/link_linux_386.go
Line 8 in 2dde2a7
There should probably be a
-l
added in front of the base library name, and a-L
for the directory.The text was updated successfully, but these errors were encountered: