Hi!
I would like to ask for some help for the bug #377468, if possible,
please. Particularly from a mozilla-plugin wizard.
The problem is that djvulibre in upstream is not linked against a particular libXt
in order to adapt against different libXt version depending of the browser used.
The question raised by the upsteam is the case of the browser itself already uses libXt, and links to
a different version of the library than the plugin.
This bug is easily demonstrable using the command [1]:
$ ldd -d -r /usr/lib/netscape/plugins-libc6/nsdejavu.so
But this behavior is quite fragile and could break [2] and I personally think that on debian browser and plugin
will use the same version of library.
Does my assertion is always valid? Can I enforce linking against libXt at build time?
BTW should we contact other plugin developper about bug like this and should we document this issue?
Regards
Bastien
--
"ROUCARIÈS Bastien"
roucaries.bastien+debian@gmail.com
-------------------------------------------------------------------------------
DO NOT WRITE TO roucaries.bastien+blackhole@gmail.com OR BE BLACKLISTED
Attachment:
signature.asc
Description: This is a digitally signed message part.