| Summary: | x11-libs/wxGTK should force bfd linker | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | David Carlos Manuelda <StormByte> |
| Component: | Current packages | Assignee: | Gentoo wxWidgets project <wxwidgets> |
| Status: | UNCONFIRMED --- | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
Tested version was x11-libs/wxGTK-3.0.4-r302 But what if GCC using people want to use ld.gold? Or is that broken for them too? (In reply to Mart Raudsepp from comment #2) > But what if GCC using people want to use ld.gold? Or is that broken for them > too? That's a good point! Tested and it does not fail with gcc (tested with 9.2.0) and gold linker. |
When trying to compile wxGTK with clang and libc++ as default (with libc++abi) it has problems with linking symbols in runtime inside its binary: /usr/bin/wxrc-3.0-gtk3 Because of this, anything can be linked/compiled against wxGTK (poedit in my testcase). When executed that binary, it tells: /usr/bin/wxrc-3.0-gtk3: /usr/lib64/libc++abi.so.1: version `WXU_3.0' not found (required by /usr/bin/wxrc-3.0-gtk3) And so anything can be compiled against it, like the mentioned poedit. Digging into the issue I found out that forcing BFD linker via LDFLAGS="${LDFLAGS} -fuse-ld=bfd" (so, forcedfully setting BFD linker) makes this problem to go away, this might be safe for gcc builds as well.