FS#41490 - linphone wont start because libpolarssl.so.6 does not exists
Attached to Project:
Community Packages
Opened by JoKoT3 (JoKoT3) - Wednesday, 06 August 2014, 16:19 GMT
Last edited by Dave Reisner (falconindy) - Wednesday, 06 August 2014, 18:41 GMT
Opened by JoKoT3 (JoKoT3) - Wednesday, 06 August 2014, 16:19 GMT
Last edited by Dave Reisner (falconindy) - Wednesday, 06 August 2014, 18:41 GMT
|
Details
Description:
A recent update of polarssl replaced /usr/lib/libpolarssl.so.6 by libpolarssl.so.7. The current version of linphone has been compiled with libpolarssh.so.6 as shown by ldd /usr/bin/linphone Linephone refuse to start with the following error : linphone: error while loading shared libraries: libpolarssl.so.6: cannot open shared object file: No such file or directory Additional info: * linphone 3.7.0-1 * polarssl 1.3.8-3 Futhermore, the current package of linphone does not depend on polarssl (nor belle-sip) but I didn't check if it was a nested depend. Steps to reproduce: upgrade polarssl launch linphone error Workaround : ln -s /usr/lib/libpolarssl.so.7 /usr/lib/libpolarssl.so.6 |
This task depends upon
Closed by Dave Reisner (falconindy)
Wednesday, 06 August 2014, 18:41 GMT
Reason for closing: Not a bug
Additional comments about closing: User error.
Wednesday, 06 August 2014, 18:41 GMT
Reason for closing: Not a bug
Additional comments about closing: User error.
- Add polarssl as a dependency to belle-sip (or name it belle-sip-polarssl providing and conflicting belle-sip)
- compile and install
I have uploaded my PKGBUILD at http://pastebin.ca/2829678
No, this doesn't show a dependency. ldd is recursive. Use readelf if you want to know the dependencies of the linphone binary.
There's been no "recent" update to polarssl which caused this. I suspect you have some AUR package (as a dep of linphone) which is linked against old polarssl causing your problem. polarssl was only recently moved into [community], while linphone has been in [community] for quite some time. So, this bug report doesn't make a whole lot of sense.
If you want to determine what binary is *actually* requesting libpolarssl, then you can run "LD_DEBUG=files linphone" to find out...
linphone 3.7.0-1 was built on Thu 13 Mar 2014.
Polarssl was brought into [community] on Thu 31 Jul 2014.
Polarssl did not exist when linphone was built.
There has never been a soname bump of the official polarssl package.
There has not yet been an update of the official polarssl package.
Symlinking sonames is a horrible idea that results in much pain.
Possibly these errors were caused by building packages in a dirty chroot that somehow had AUR packages installed?
I now recall that I did pretty much as IncredibleLaser describes because I needed to use SSL in linphone.
I carelessly enabled polarssl support in build() but did not take the precaution to rename and add provides+conflicts to the PKGBUILD.
I apologize for the inconvenience.
On the subject of belle-sip and polarssl ; I think that since polarssl is now in community, it might be a good idea to provide belle-sip package with polarssl enabled.
Feel free to open a new feature request with explanation and technical reasoning.