On Thu, Jan 8, 2009 at 3:21 PM, James Ausmus <james.aus...@gmail.com> wrote: > > > On Thu, Jan 8, 2009 at 2:35 PM, Mark Knecht <markkne...@gmail.com> wrote: >> >> On Thu, Jan 8, 2009 at 12:02 PM, James Ausmus <james.aus...@gmail.com> >> wrote: >> <NIP> >> >> >> > a "ls /usr/lib/nss/libnss3*"? >> >> >> > >> >> >> lightning ~ # ls /usr/lib/nss/libnss3* >> >> >> /usr/lib/nss/libnss3.so /usr/lib/nss/libnss3.so.11 >> >> >> /usr/lib/nss/libnss3.so.12 >> >> >> lightning ~ # >> >> > >> >> > Aha! And which of the versioned .so's is libnss3.so linking to? >> >> > >> >> lightning ~ # ls -l /usr/lib/nss/libnss3* >> >> lrwxrwxrwx 1 root root 13 2009-01-08 10:00 >> >> /usr/lib/nss/libnss3.so -> libnss3.so.12 >> >> -rwxr-xr-x 1 root root 560376 2008-11-25 17:02 >> >> /usr/lib/nss/libnss3.so.11 >> >> -rwxr-xr-x 1 root root 1337104 2009-01-08 10:00 >> >> /usr/lib/nss/libnss3.so.12 >> >> lightning ~ # >> > >> > Hmm - very odd - seems that the evolution build is specifically grabbing >> > the >> > libnss3.so.11 version... Maybe try running "ldconfig"? If that doesn't >> > work, >> > maybe try deleting (or renaming, if you're paranoid ;) ) libnss3.so.11 >> > (and >> > all other .so.11's that you find in /usr/lib/nss). >> > Anyone else have any better ideas? >> > -James >> > >> >> Do I just run ldconfig or are there options/paths I have to give it. >> Should I run ldconfig -p and post anything back or is it safe to run. >> It looks like /etc/ls.so.conf is a list of libraries. > > You should just be able to run "ldconfig" by itself with no options - it's > safe to run. > >> >> Would I kill the machine with an emerge -C nss and then emerge it again? > > Hmm - there are a lot of things that wouldn't run while nss was "demerged", > but, I *believe* it would be OK, as long as you ensure you have all the nss > source packages downloaded prior to the emerge -C nss - easy way to make > sure is to emerge -f nss first, then you're guaranteed that it's fully > downloaded (unless the nss build system itself does any downloading, but I > believe nss doesn't have any wonkiness in it's build system - just standard > autotools). > -James > >> >> Thanks much, >> Mark >> > > Same results emerging evolution after running ldconfig.
Other than curl which I don't know much about it seems that remving nss wouldn't be that likely to cause horrific problems: lightning ~ # equery depends nss [ Searching for packages depending on nss... ] gnome-extra/evolution-data-server-2.22.3-r1 (ssl? >=dev-libs/nss-3.9) mail-client/evolution-2.22.3.1 (ssl? >=dev-libs/nss-3.11) net-libs/xulrunner-1.8.1.19 (>=dev-libs/nss-3.11.5) net-libs/xulrunner-1.9.0.5 (>=dev-libs/nss-3.12) net-misc/curl-7.18.2 (nss & !gnutls? dev-libs/nss) net-www/netscape-flash-10.0.15.3 (x86? dev-libs/nss) www-client/mozilla-firefox-3.0.5 (>=dev-libs/nss-3.12) lightning ~ # Even with respect to curl I'm guessing it doesn't matter as I have the flag turned off and it's the only package with that flag: lightning ~ # equery hasuse nss [ Searching for USE flag nss in all categories among: ] * installed packages [I--] [ ] net-misc/curl-7.18.2 (0) lightning ~ # lightning ~ # emerge -pv curl These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] net-misc/curl-7.18.2 USE="ipv6 ldap ssl -ares -gnutls -idn -kerberos -libssh2 -nss -test" 0 kB Total: 1 package (1 reinstall), Size of downloads: 0 kB lightning ~ # I actually did an emerge -ef world already just to ensure everything is here. I'm considering the emerge -C nss, remove any links left over by hand, and then emerging evolution again and letting it pull it in and build it in one step. Comments? Thanks, Mark
