Bug#795818: libindi: FTBFS on arm64: symbols mismatch
Source: libindi
Version: 1.0.0-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)
libindi is still failing to build on arm64. The culprit seems to be lines
specific to arm64 and sh4 in the symbols file, like these:
- (arch=!arm64 !sh4)_ZN4INDI10BaseDevice10addMessageENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 1.0.0
- (arch=arm64 sh4)_ZN4INDI10BaseDevice10addMessageESs@Base 1.0.0
+ _ZN4INDI10BaseDevice10addMessageENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 1.0.0
The "official" ABI for all Debian architectures is the g++-5 one, with
__cxx11 mentioned; so IMO the correct solution to this is to make
all the symbols like
_ZN4INDI10BaseDevice10addMessageENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base
non-architecture-specific.
It is good that this would make libindi1 fail to build from source on
architectures not using g++-5, since if it built successfully there,
it would need a transition to the g++-5 ABI later.
S
Reply to: