Bug#795316: jackd2: Suggestion to fix overly-liberal shlibs for libjacknet
jcowgill at debian.org
Wed Oct 19 10:24:06 UTC 2016
Control: tags -1 - patch
On Wed, 12 Aug 2015 14:38:38 -0700 Steve Langasek
<steve.langasek at canonical.com> wrote:
> Package: jackd2
> Version: 1.9.10+20140719git3eb0ae6a~dfsg-3
> Severity: normal
> Tags: patch
> User: ubuntu-devel at lists.ubuntu.com
> Usertags: origin-ubuntu wily ubuntu-patch
> Dear maintainer,
> I know you've only just fixed the shlibs file to correct jackd2's FTBFS
> failure, but I'd like to recommend a change to the shlibs handling. As part
> of preparing the g++5 ABI transition in Ubuntu, it came to light that:
> - libjacknet is a private library, and
> - its ABI is impacted by the g++5 ABI transition
> So while the current shlibs fix the build failure, in the unlikely event
> that something *did* link against libjacknet (unlikely because it's a
> private library with no headers in the -dev package), that package would
> have a wrong dependency, which would be satisfied by other versions of the
> package with known-incompatible ABI.
As far as I can tell (as I don't deal much with jack), libjacknet is not
a private library. It is used to create network slaves which communicate
with a jack server over the network. The header for it is
Also, I don't think it is affected by the g++5 ABI transition because
all the C++ symbols are not part of the ABI - the main API is C (the C++
symbols should probably be hidden).
I think the best solution is to move it into a separate package since
the library is not used much (compared to the main jack client library).
Having said that, it's not too important as I don't think there are any
ABI issues here.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 819 bytes
Desc: OpenPGP digital signature
More information about the pkg-multimedia-maintainers