| commit | c2755a52aa36959508e68cf0ae79833bba624cf0 | |
| author | Jakub Adam <jakub.adam@ktknet.cz> | |
| Wed, 10 Jun 2015 12:44:42 +0000 (10 14:44 +0200) | ||
| committer | Jakub Adam <jakub.adam@ktknet.cz> | |
| Fri, 12 Jun 2015 08:29:06 +0000 (12 10:29 +0200) | ||
| tree | b1dba9c93afb9e27221d83a67167aac327cf9a5e | treesnapshot (tar.gz zip) |
| parent | 2aebcef0abe37eb6b8e9bc18c0c3be2da82aec76 | commitdiff |
purple: avoid function name clash with SIMPLE plugin
SIMPLE libpurple plugin exports a couple of functions having the same
names as Sipe uses - sipmsg_free() for example. Under some circumstances
(plugins loaded in a different order?), the dynamic linker may bind
references in libsipe.so to the functions in libsimple.so, which leads
to an unpredictable behavior at runtime.
Linking with -Bsymbolic-functions makes Sipe always use the function
definitions within our shared library.
SIMPLE libpurple plugin exports a couple of functions having the same
names as Sipe uses - sipmsg_free() for example. Under some circumstances
(plugins loaded in a different order?), the dynamic linker may bind
references in libsipe.so to the functions in libsimple.so, which leads
to an unpredictable behavior at runtime.
Linking with -Bsymbolic-functions makes Sipe always use the function
definitions within our shared library.
| src/purple/Makefile.am | diffblobblamehistory |