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/link: handle repeated "unresolved inter-package jump" errors #25753
Comments
I'll send a fix today. |
Change https://golang.org/cl/116676 mentions this issue: |
For the record observed on pp64le/armv7hl Fedora and Epel/RHEL/Centos 7 where it breaks build of the GC as all test passing is expected.
CL116676 seems to resolve this issue for me. |
This resolves the issue, can we get this fix in? |
@laboger, sorry for the inconvenience. If anyone familiar with Go linker can help Ian doing a review, maybe we can get this faster. |
@quasilyte I'm waiting for an updated change on https://golang.org/cl/116676. You replied to my comments but you didn't upload any fixes. Or did I miss something? |
My mistake. Updated patch set was not sent. :( |
CL113955 fixes duplicated "unresolved symbol" messages, but for architectures with trampoline support we also have "unresolved inter-package jump" errors (they are also repeated).
This caused some builders to break due to failing
TestUndefinedRelocErrors
test.Given program used in test:
With pre-updated linker we get and
GOARCH=ppc64
:With CL mentioned above we get less errors, but some unexpected and duplicated errors remain:
Leading to failure:
The text was updated successfully, but these errors were encountered: