[MacPorts] #71463: wxWidgets: any way to avoid ABI mismatch errors due to updated compiler?
MacPorts
noreply at macports.org
Thu Dec 5 15:31:17 UTC 2024
#71463: wxWidgets: any way to avoid ABI mismatch errors due to updated compiler?
--------------------------+-----------------------
Reporter: barracuda156 | Owner: (none)
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 2.10.5
Keywords: | Port: wxWidgets
--------------------------+-----------------------
I have seen this error a number of times. Apparently this results from
either `wxWidgets` or a dependent being rebuilt with a newer version of
compiler (though it is unclear what exactly counts as "newer" in this
context).
{{{
36-174% /Applications/MacPorts/wxHexEditor.app/Contents/MacOS/wxHexEditor
Fatal Error: Mismatch between the program and library build versions
detected.
The library used 3.0 (wchar_t,compiler with C++ ABI 1019,wx
containers,compatible with 2.8),
and your program used 3.0 (wchar_t,compiler with C++ ABI 1018,wx
containers,compatible with 2.8).
}}}
The nasty thing is that this output is available only when the binary is
launched from command line, while if it is launched as Mac app, it just
crashes with an obscure output. So a user may just assume the app is
broken.
Is there any solution to this besides revbumping all wxWidgets dependents
upon every update of the primary compiler and/or runtime?
I do not think the apps are in fact incompatible, it is probably some
mechanism in wxWidgets which is fine for a static environment like a given
macOS version with default Apple compilers, but leads to unneeded troubles
otherwise.
--
Ticket URL: <https://trac.macports.org/ticket/71463>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list