another quick update base on a discussion between nacc/slangasek and myself :
...
<nacc> slangasek: fair, above patch results in https://paste.ubuntu.com/p/hb68G8rpMw/
<slangasek> nacc: those are pretty clearly internal symbols which are not part of the ABI and you should just mark them (optional) instead of doing an architecture-based exclusion list
<slangasek> and when I say mark them (optional), I mean mark them '(optional)'
<slangasek> nacc: dropping the symbols, or marking them optional, both valid. (optional) would make the same source package more cleanly backportable to older toolchains
<slangasek> but a symbol that starts with a __ and isn't listed in the public headers for the library, and especially that doesn't originate in the source of this library, can be assumed safe to drop from .symbols
another quick update base on a discussion between nacc/slangasek and myself :
... /paste. ubuntu. com/p/hb68G8rpM w/
<nacc> slangasek: fair, above patch results in https:/
<slangasek> nacc: those are pretty clearly internal symbols which are not part of the ABI and you should just mark them (optional) instead of doing an architecture-based exclusion list
<slangasek> and when I say mark them (optional), I mean mark them '(optional)'
<slangasek> nacc: dropping the symbols, or marking them optional, both valid. (optional) would make the same source package more cleanly backportable to older toolchains
<slangasek> but a symbol that starts with a __ and isn't listed in the public headers for the library, and especially that doesn't originate in the source of this library, can be assumed safe to drop from .symbols