-
Notifications
You must be signed in to change notification settings - Fork 18k
cmd/link: linking fails with some PE imported libraries #38951
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
Comments
Thanks for submitting this issue.
Could you please attach the text of the error (including stack trace) to the bug? Thanks. |
@thanm I believe I was not super accurate in explaining the issue. The linker does not throw an error actually. Error produces by the
|
@thanm I did a bit of investigation and found out that as a part of fixing security issues in So, I believe it is fine and we can close the issue as there is no regression, or at least it is a part of mitigating security issues. @thanm If you feel the same please close the issue |
Thanks, makes sense. Closing out the issue. |
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
)?go env
OutputWhat did you do?
I created a repository https://github.com/Neurostep/go-link-test where I put everything to reproduce the issue.
If you clone the provided repo and try to run
BUILDER_IMAGE=neurostep/go-linker-test:go114 ./run.sh
, you should see the linker throws an error.If you run
BUILDER_IMAGE=neurostep/go-linker-test:go112 ./run.sh
the build creates just fine.What did you expect to see?
I expect to see PE imported libs
ws2_32
andwinmm
are linked as it did before go version 1.13.Here I put the host link output only
What did you see instead?
Here I put the host link output only
The text was updated successfully, but these errors were encountered: