-
Notifications
You must be signed in to change notification settings - Fork 651
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
fatal error: invalid function symbol table
when using cgo starting in go 1.21
#4091
Comments
To add to the issue, I've also had to workaround this using toolchains_musl and a combination of the pure setting. |
I thought this might be fixed by #3691 but no luck. I did notice that passing |
Thanks for the repro. This is actually a combination of two things happening.
|
If the placeholder mechanism needs to stay, then I think the only solution is for the linker to also have a wrapper like cc.go. I am not current in the codebase and I won't have the time to implement a proper solution here, so would appreciate if someone else takes over. |
Also filed golang/go#69350 to eventually fix the issue upstream. |
Cc @AlessandroPatti for the wrapper |
What version of rules_go are you using?
0.50.1
What version of gazelle are you using?
0.38
What version of Bazel are you using?
7.2.1
Does this issue reproduce with the latest releases of all the above?
yes
What did you do?
See https://github.com/DavidZbarsky-at/cgo-repro for repro
This was not an issue with go 1.20.1 but is an issue starting in 1.21
See https://github.com/google/skia/blob/main/.bazelrc#L41-L45 for another example in the wild
What did you expect to see?
No-op binary runs correctly
What did you see instead?
The text was updated successfully, but these errors were encountered: