Ubuntu
nss package

  1. Bug #244439
  2. Comment #5

Comment 5 for bug 244439

Revision history for this message
In , Dolske (dolske) wrote :

Hmm. Yeah, we do seem to need to link against libnspr and friends. Otherwise building the component fails.

On the VM where I can reproduce the problem, "ldd WeaveCrypto.so" reports that it can't find libxpcom.so, libnspr4.so, libsmime3.so, libssl3.so, libnss3.so, libnssutil3.so, libplds4.so, and libplc4.so. On my build machine, these are all found in /usr/lib (presumably put there by the build-dep packages I have installed). [Well, libxpcom.so isn't found but it works anyway; I guess the xpcomglue_s that's linked in is taking care of this at runtime?]

I also found: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/228032

...which makes me suspect this is a Debian/Ubuntu bug. And I found bsmedberg's old "Debian Versioning of Mozilla Libraries Harmful" blog post, which also makes me wonder just what's supposed to be happening here. :/

Suggestions? Does Weave need to link differently, or is this a Ubuntu bug?