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: incorrect relocations during external linking on linux/386 with musl libc #14478
Comments
Is this a tracking bug for the other being in 1.6.1 or a separate bug? If it's a separate bug maybe it can wait until 1.6.3. |
this is a separate bug: external linking doesn't work on linux/386 with
musl libc.
I don't know what's wrong yet....
|
Given there's no fix, it seems like this should be at least investigated for Go 1.7. It won't be in Go 1.6.3 (which probably won't happen). |
This would be nice to fix but it doesn't seem to be happening. Dropping to 1.8. |
The relevant part of Minux's comment from #14476: An externally linked hello world program couldn't even start: Program received signal SIGSEGV, Segmentation fault. Something is wrong with the relocations. |
This doesn't seem like it is affecting many people. Moving to Go1.8Maybe. |
Is this still a problem? |
Timed out in state WaitingForInfo. Closing. (I am just a bot, though. Please speak up if this is a mistake or you have the requested information.) |
See #14476 (comment)
Tentatively labeled Go1.6.1, but it probably doesn't meet the line.
The text was updated successfully, but these errors were encountered: