On Fri, Dec 06, 2019 at 05:37:25PM +0100, Ole Streicher wrote: > Hi, > > for the "casacore" package (written in C++), we wanted to introduce > symbols files for the shared libraries it produces. However, this > somehow does not work, as they seem to depend on the architecture and/or > the C++ compiler version: > > https://buildd.debian.org/status/logs.php?pkg=casacore&ver=3.2.1-1 > > shows the build failures for the same package that compiled well on > x86_64 caused by differences in the symbols table. > > How should one handle this? My favorite answer for that is in the Policy section 8.6: """ For most C libraries, the additional detail required by symbols files is not too difficult to maintain. However, maintaining exhaustive symbols information for a C++ library can be quite onerous, so shlibs files may be more appropriate for most C++ libraries. """ If you still want symbols there is pkgkde-gensymbols(1) in pkg-kde-tools and maybe other options. -- WBR, wRAR
Attachment:
signature.asc
Description: PGP signature