I have now switched JACK packaging to use symbols files, to automate tracking of ABI changes.

The switch from 0.118 to 1.9.5 causes breakage in that automated tracking, however.

It might be that there are some ABI breakaage after all, but possibly it is just private symbols not detected as such by the routines.

More on the routine here: http://wiki.debian.org/UsingSymbolsFiles

For now I simply threw in the hints from http://qa.debian.org/cgi-bin/mole/seedsymbols/?pkgname=libjack0 - that needs quite some cleanup, both in unifying parts identical across several/all architectures, and adjusting the initial release of introduction of each symbol. I just wanted to have someone look into the issue of breakage before cleaning up.

For an example (that I am familiar with, since I did it myself) on sharing symbol hints across architectures, see the source of the ghostscript packaging.

Can someone fluent in C/C++ please look at this? Perhaps you, Adrian, since you seem most knowledgeable in JACK around here?

Kind regards,

 - Jonas

* Jonas Smedegaard - idealist & Internet-arkitekt
* Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

Attachment: signature.asc
Description: Digital signature

pkg-multimedia-maintainers mailing list

Reply via email to