Hello, I have some questions about the handling of symbols files at Debian.
The quotes based on the package bitz-server[1]. My symbols file are[2]: [quote] libicap.so.1 libicap1 #MINVER# (c++)"icap::RequestHeader::read_header(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)@Base" 1.0.0 (c++)"icap::RequestHeader::RequestHeader(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)@Base" 1.0.0 (c++)"icap::RequestHeader::RequestHeader(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)@Base" 1.0.0 [/quote] The result after building the amd64 binaries are[3]: [quote] libicap.so.1 libicap1 #MINVER# _ZN4icap13RequestHeader11read_headerERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 1.0.0 _ZN4icap13RequestHeaderC1ERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 1.0.0 _ZN4icap13RequestHeaderC2ERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 1.0.0 [/quote] The building at armel[4] fails with: [quote] --- debian/libicap1.symbols (libicap1_1.0.0-1_armel) +++ dpkg-gensymbols782sDG 2016-02-12 21:11:15.078848642 +0000 @@ -1,4 +1,6 @@ libicap.so.1 libicap1 #MINVER# + _ZSt13__adjust_heapIN9__gnu_cxx17__normal_iteratorIPSt4pairINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEiESt6vectorIS9_SaIS9_EEEEiS9_NS0_5__ops15_Iter_comp_iterIN4icap6Header27encapsulated_header_compareEEEEvT_T0_SM_T1_T2_@Base 1.0.0-1 + _ZSt16__introsort_loopIN9__gnu_cxx17__normal_iteratorIPSt4pairINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEiESt6vectorIS9_SaIS9_EEEEiNS0_5__ops15_Iter_comp_iterIN4icap6Header27encapsulated_header_compareEEEEvT_SL_T0_T1_@Base 1.0.0-1 (c++)"__gnu_cxx::__normal_iterator<char*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > std::__find_if<__gnu_cxx::__normal_iterator<char*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, __gnu_cxx::__ops::_Iter_pred<std::unary_negate<std::pointer_to_unary_function<int, int> > > >(__gnu_cxx::__normal_iterator<char*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, __gnu_cxx::__normal_iterator<char*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, __gnu_cxx::__ops::_Iter_pred<std::unary_negate<std::pointer_to_unary_function<int, int> > >, std::random_access_iterator_tag)@Base" 1.0.0 (c++)"icap::Header::Header()@Base" 1.0.0 (c++)"icap::Header::attach(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >)@Base" 1.0.0 @@ -64,18 +66,18 @@ [/quote] The result looks like that all builds use an other symbols file as base, because already the second line differs from the original. Why? And from where comes the used symbols file? This circumstance also prevents the simple use of patch. Is there a plan to change it? And what is the best way to maintain it? Nice Weekend.. CU Jörg [1] https://tracker.debian.org/pkg/bitz-server [2] http://httpredir.debian.org/debian/pool/main/b/bitz-server/bitz-server_1.0.0-1.dsc [3] http://ftp.de.debian.org/debian/pool/main/b/bitz-server/libicap1_1.0.0-1_amd64.deb [4] https://buildd.debian.org/status/fetch.php?pkg=bitz-server&arch=armel&ver=1.0.0-1&stamp=1455311478 -- New: GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D GPG key (long) : 09F89F3C8CA1D25D GPG Key : 8CA1D25D CAcert Key S/N : 0E:D4:56 Old pgp Key: BE581B6E (revoked since 2014-12-31). Jörg Frings-Fürst D-54538 Bausendorf Threema: SYR8SJXB IRC: j_...@freenode.net j_...@oftc.net My wish list: - Please send me a picture from the nature at your home.
signature.asc
Description: This is a digitally signed message part
