[Pkg-lxqt-devel] Bug#798050: qtermwidget: FTBFS: symbols not as expected

Aaron M. Ucko ucko at debian.org
Fri Sep 4 20:04:29 UTC 2015

Source: qtermwidget
Version: 0.6.0-1
Severity: serious
Justification: fails to build from source

Automated builds of qtermwidget on Linux have been failing because the
set of (mangled) symbol names wasn't quite as expected, as detailed at
https://buildd.debian.org/status/logs.php?pkg=qtermwidget&ver=0.6.0-1 .
(The kFreeBSD builds failed due to a totally unrelated issue, which
I'll report separately.)

There are actually two problems (which perhaps deserve separate reports):

* On 32-bit architectures such as i386, a number of symbols have
  different names; I suspect most of these discrepancies stem from
  differences in size_t's ultimate type (unsigned int on 32-bit
  platforms, unsigned long on 64-bit ones).  Please account for these
  differences, either directly or with the help of
  pkgkde-symbolshelper et al. from pkg-kde-tools.

* Even on 64-bit architectures such as arm64,
  QList<QString>::operator+=(QList<QString> const&)@Base is missing.
  I suspect the issue here to be that some build dependency changed
  while qtermwidget was in NEW, so I used severity serious because an
  amd64 rebuild could well encounter the same error.  That said, all
  symbols from Qt headers are presumably internal implementation
  details; I see no way to blacklist them altogether when processing
  the .symbols file, but you can at least mark them as optional to
  indicate that it's no big deal if any wind up disappearing.  (A
  better solution would be to hide these symbols via a linker script,
  but I don't know how feasible that would be.)

Could you please take a look?


More information about the Pkg-lxqt-devel mailing list