On Thu, Jan 8, 2009 at 2:35 PM, Mark Knecht <[email protected]> wrote:

> On Thu, Jan 8, 2009 at 12:02 PM, James Ausmus <[email protected]>
> 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
>
>

Reply via email to