> I suspect that many optional symbols on the symbols file of this package > could be squashed with a regex, but alas I can't help with that now > since I'll be soon leaving for a 2-weeks travel and I don't think I > would ever find the time to also look at this. Anyway, look at the gdcm > repo for an idea of what I'm talking about.
Not sure if a regex is appropriate here, since some of the symbols come and go, depending on the compiler, dependencies and architecture. But I'll take look, thanks for the hint. > Anyway, the problem that dpkg-gensymbols is complaining about, it's > because you missed a quote sign in > a4f32173da0f7ab5c173d89fd556f0af242d2deb (didn't you notice this while > test building before asking for sponsorship?). Ouch, thanks for pointing that out. I totally didn't see this. Thought there was something wrong with the Debian-tagged version I added. > After that my local build failed because I locally export > DPKG_GENSYMBOLS_CHECK_LEVEL=4 and it seems this new symbol is new: > > _ZNSt10_HashtableIPKN6google8protobuf10DescriptorESt4pairIKS4_jESaIS7_ENSt8__detail10_Select1stESt8equal_toIS4_ESt4hashIS4_ENS9_18_Mod_range_hashingENS9_20_Default_ranged_hashENS9_20_Prime_rehash_policyENS9_17_Hashtable_traitsILb0ELb0ELb1EEEE21_M_insert_unique_nodeEmmPNS9_10_Hash_nodeIS7_Lb0EEEm@Base>> Anyway, that's yet another std:: function leaked from who knows where, > so nvm that… I'll raise the issue on the developer's issue tracker and see if I can send them a patch. Far too much time has been wasted on this already.
