-
Notifications
You must be signed in to change notification settings - Fork 18.1k
cmd/link: RISC-V external link, failed to find text symbol for HI20 relocation #65646
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
We are facing the same issue in rqlite/rqlite#1682. |
cc @golang/riscv64 @golang/compiler |
As an update, this failure seems to go away if I revert CL 520095. |
That CL addresses #62465, so we probably could not simply revert. |
Change https://go.dev/cl/567375 mentions this issue: |
Build fails with following errors: > failed to find text symbol for HI20 relocation at 17057632 (1044760) > github.com/aws/aws-sdk-go/aws/endpoints.init: unsupported obj reloc 62 (R_RISCV_CALL)/8 to runtime.morestack_noctxt > [...] > failed to find text symbol for HI20 relocation at 17058056 (1044908) > /usr/lib/go/pkg/tool/linux_riscv64/link: too many errors > >>> ERROR: grype: build failed Relevant issue for Go compiler: golang/go#65646
@cherrymui seems like something we could/should backport? It can be avoided/worked around by using internal linking, rather than forcing external linking. |
I think it is reasonable to backport. Internal linking is not the default mode, and has limitations. @gopherbot please backport this to Go 1.22. Thanks. |
Backport issue(s) opened: #66060 (for 1.22). Remember to create the cherry-pick CL(s) as soon as the patch is submitted to master, according to https://go.dev/wiki/MinorReleases. |
Go does not support internal linking while -buildmode=pie on riscv64. Enable CGO on riscv64 as well. See: golang/go#65646
[ commit b2e16837fb881e4e31a23ab492a69082f98e9f7d ] See: * golang/go#65646 * https://go-review.googlesource.com/c/go/+/567375
Uh oh!
There was an error while loading. Please reload this page.
Go version
go version go1.22.0 linux/riscv64
Output of
go env
in your module/workspace:What did you do?
What did you see happen?
What did you expect to see?
Build successfully.
A successor of #62465 , but no the same issue.
The text was updated successfully, but these errors were encountered: