You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is clearly related to CGo somehow and I think it may be caused by a signature mismatch. There are two symbols with the same name and a different signature. One lives in the Go package as a .cpp file, the other is declared in a header file (included by CGo) and lives in an archive file. My theory is that CGo picks the one at one time and a different one some other time which leads to a conflict.
That's a lot of guessing and little reproducing. But this is a large and complicated system and I'm not sure how to make it smaller, but perhaps you can see something that is wrong so I can look into it further?
Tested with two different system linkers: ld.bfd and ld.lld-8.
Tell us exactly what you did and exactly what happened. Not just a single snippet from the output. Thanks.
Also, if you are using the original Go 1.12 release as suggested above, try the Go 1.12.5 release. There have been some bug fixes that may be relevant.
julieqiu
added
the
WaitingForInfo
Issue is not actionable because of missing required information, which needs to be provided.
label
May 28, 2019
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes, with Go compiled from 45d74aa.
What operating system and processor architecture are you using (
go env
)?go env
OutputReproducing
I'm not exactly sure how to reproduce this yet, but this is the error I'm getting:
It is clearly related to CGo somehow and I think it may be caused by a signature mismatch. There are two symbols with the same name and a different signature. One lives in the Go package as a .cpp file, the other is declared in a header file (included by CGo) and lives in an archive file. My theory is that CGo picks the one at one time and a different one some other time which leads to a conflict.
That's a lot of guessing and little reproducing. But this is a large and complicated system and I'm not sure how to make it smaller, but perhaps you can see something that is wrong so I can look into it further?
Tested with two different system linkers:
ld.bfd
andld.lld-8
.Sort-of related:
https://reviews.llvm.org/D60484
https://reviews.llvm.org/rL358086
Also: this is with Go modules disabled, if that is relevant.
The text was updated successfully, but these errors were encountered: