Mark, sorry for causing trouble here - I'm in the process to do a "offical" release libzrtpcpp in 2-3 weeks after some more regressions with the original Zfone implementation. The ZRTP specifications changes quite a lot, thus the ABI is incompatible. The best way to overcome this is to recompile twinkle with the new libzrtcpp files (headers and alike).
Regards, Werner Mark Purcell wrote: > Werner, > > It appears that your latest libzrtpcpp breaks it's ABI, but doesn't > bump the soname. This breaks binary compatibility for binary > distributions like Debian. > > http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=libzrtpcpp > > We are going to make a local patch to the Debian package, but you might > also like to make a more official soname change upstream. > > Btw, we have a package tracking system that anyone can subscribe to > via email and that way you can receive bug reports like this as we do ;-) > > http://packages.qa.debian.org/libzrtpcpp > > Mark > > ---------- Forwarded Message ---------- > > Subject: ABI changed without a corresponding soname change > Date: Thu, 11 Oct 2007 > From: Mikael Magnusson <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > > Piotr Kaczuba wrote: >> When the "Enable ZRTP/SRTP encryption" option is checked, twinkle >> crashes as soon as one makes or answers a call. >> >> This is what is printed in a terminal: >> >> twinkle: symbol lookup error: twinkle: undefined symbol: >> _ZThn580_N3ost9ZrtpQueue11sendDataRTPEPKhi > > The error is caused by API (and ABI) changes in libzrtpcpp version > 0.9.2. The symbol above (sendDataRTP) is removed and seems to be > replaced with sendDataZRTP, without changing the SONAME. > > > > > > > ------------------------------------------------------- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]