Ruchi Lohani wrote, On 2008-07-18 11:06: > It gives the version as NSS 3.12.0.2. > > The problem I am facing is when I build my program on ubuntu linking to > nss and nspr it works fine on Ubuntu but when I try to use the same > library built on Ubuntu on Suse its unable to resolve the symbols and I > get the following messages > When I do 'ld' on the library. > > ld: warning: libssl3.so.1d, needed by **** not found > ld: warning: libnss3.so.1d, needed by **** not found > ld: warning: libnspr4.so.0d, needed by **** not found > > and then the messages like > : undefined reference to [EMAIL PROTECTED]' > : undefined reference to [EMAIL PROTECTED]' > : undefined reference to [EMAIL PROTECTED]' > : undefined reference to `PR_Initialized' > : undefined reference to [EMAIL PROTECTED]'
The problems that you have observed and reported clearly indicate that the NSS libraries you're using have been altered in ways that make them, and programs linked with them, incompatible with NSS (and programs that use it) on other platforms (other Linux distros). When one sees changes of this magnitude, one wonders what other changes have been made to NSS, and one recalls the utterly disastrous changes that were made by tinkering with OpenSSL. My advice is: don't use crypto libraries that have been altered from the version that was QAed and released by the upstream team where the package originates. Even if you have to build and distribute your own copy, that's more advisable, in my opinion, than relying on a version with alterations of unknown magnitude, and/or with dubious value. I intend for that advice to apply to all crypto libraries, and not only to NSS. _______________________________________________ dev-tech-crypto mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-crypto
