-
Notifications
You must be signed in to change notification settings - Fork 80
__compact_unwind linker issue (possibly darwin specific) #146
Comments
No idea I'm afraid. Looks like wonky DWARF/debug metadata, but I'm not really sure. |
Ah. I know this one. And yes, its very Darwin specific. Apple screwed up back during the https://llvm.org/svn/llvm-project/libcxxabi/trunk/include/unwind.h The short of it is that the GCC support libraries on Darwin were never fixed (and aren't to this day). Apple walked away, re-implimented them all entirely; and from what I can gather, the GNU libs are perma-wontfix in GCC upstream. Amongst other things, this affair is responsible for things like:
I'm not really familiar with your project (I stumbled on this issue trying to figure out if the golang "6l" linker implements a true, non-ld64-wrapping, independent linker on Darwin. Anyone know?), but if I had to guess, this looks to be a good candidate for why you're seeing this (generally speaking): https://github.com/go-llvm/llgo/blob/master/cmd/llgo-build/build.go#L290 Basically, you really don't wan't to be doing that on this platform. Its a pretty a toxic combination. Should be avoided if at all possible, for a host of reasons besides this one (linkage dependency, etc). But perhaps its unavoidable here (?), i.e., by virtue of the fact that, (last I checked?) GCC Go can't be built against either libc++ or Apple's old libstdc++, but only late-model libstdc++? Anyway… hope that helps a bit. P.S. |
It does, compare output of |
Didn't find one for this one neither, and it still happens (also originally from #70 (comment)). Any ideas?
The text was updated successfully, but these errors were encountered: