1 |
Am Donnerstag 17 September 2009 19:21:44 schrieb walt: |
2 |
> Two days ago after updating world on my ~amd64, at least two apps |
3 |
> can't find libssl.so.12 even though it's right where it should be. |
4 |
> |
5 |
> One difference I find between my working x86 and my broken ~amd64 |
6 |
> is the output of ldconfig -p: |
7 |
> |
8 |
> x86 machine: |
9 |
> #ldconfig -p | grep ssl3.so |
10 |
> libssl3.so.12 (libc6) => /usr/lib/nss/libssl3.so.12 <== minor number |
11 |
> libssl3.so (libc6) => /usr/lib/nss/libssl3.so |
12 |
> |
13 |
> ~amd64 machine: |
14 |
> #ldconfig -p | grep ssl3.do |
15 |
> libssl3.so (libc6,x86-64) => /usr/lib64/nss/libssl3.so |
16 |
> libssl3.so (libc6) => /opt/flash-libcompat/libssl3.so |
17 |
> |
18 |
> Note that the minor number (.12) doesn't show up even though there |
19 |
> is a correct and proper symlink for it in /usr/lib64/nss. |
20 |
> |
21 |
> Another source of confusion for me is that the programs that need |
22 |
> libssl3.so.12 are both linked against libssl3.so (no minor number) |
23 |
> but the error message specifically says that libssl3.so.12 can't be |
24 |
> found. |
25 |
> |
26 |
> Can anyone here make sense out of this info? |
27 |
|
28 |
Not really, but I've seen this on my box at work today. The interesting thing |
29 |
here was that for the affected program, evolution, libssl3.so showed up four |
30 |
times in ldd output, where three entries showed "not found" while the forth |
31 |
showed the location of the lib. |
32 |
|
33 |
Interestingly, setting LD_LIBRARY_PATH to /usr/lib/nss resolved the issue. |
34 |
|
35 |
Bye... |
36 |
|
37 |
Dirk |