On Wed, Jul 23, 2008 at 5:30 PM, Ruchi Lohani <[EMAIL PROTECTED]> wrote: > Found this in Ubuntu bugs > https://bugs.launchpad.net/ubuntu/+source/libnss-db/+bug/238500 > > Even though there are symlinks for each library but the SONAME differs > for all on Ubuntu and any other > Linux distribution. On Ubuntu > objdump -p /usr/lib/libnss3.so | grep SONAME > gives libnss3.so.1d where as on Suse (or probably many other Linux) its > libnss3.so, so the problem > that I face is obvious, though it works the opposite way (Building on > Suse and running it on Ubuntu). > > I don't know whom to blame :-) I guess probably not use ubuntu for > building.
Re: the SONAME issue NSS's SONAME naming convention is: libfoo<major-version>.so The standard SONAME naming convention on Solaris and Linux is: libfoo.so.<major-version> It is true that NSS's naming convention is nonstandard, but it is essentially the same as the standard convention. For backward compatibility we can't change our naming convention. So, a SONAME like libnss3.so.1d is like: libfoo<major-version>.so.<made-up-major-version> The "1d" major version that they made up is extraneous. It makes the SONAME comply to the standard naming convention superficially, but doesn't accomplish anything else. Moreover, it prevents people from using binaries embedded with this SONAME on other Linux distributions. Wan-Teh (Note: Our naming convention was defined in 1997 or 1998. I didn't know about the standard naming convention back then. Perhaps I was ignorant, or perhaps the standard naming convention didn't exist then.) _______________________________________________ dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-crypto
