1 |
On 01/24/13 19:25, Alan Mackenzie wrote: |
2 |
> Hi, Gentoo! |
3 |
> |
4 |
> A couple of days ago, I merged firefox-17.0.2 and ran revdep-rebuild -p. |
5 |
> It said, strangely, that some firefox libraries needed rebuilding. |
6 |
> |
7 |
> I've just let revdep-rebuild rebuild firefox. I run revdep-rebuild -p |
8 |
> again, and it's still saying these libraries need rebuilding. This |
9 |
> isn't good. |
10 |
> |
11 |
> Here's some output from revdep-rebuild -p: |
12 |
> |
13 |
> * Checking dynamic linking consistency |
14 |
> [ 100% ]Same problem |
15 |
> * broken /usr/lib64/firefox/libxpcom.so (no version information available) |
16 |
> * broken /usr/lib64/firefox/plugin-container (no version information available) |
17 |
> * broken /usr/lib64/firefox/sdk/bin/xpcshell (no version information available) |
18 |
> * broken /usr/lib64/firefox/sdk/lib/libxpcom.so (no version information available) |
19 |
> * Generated new 3_broken.rr |
20 |
> * Assigning files to packages |
21 |
> * /usr/lib64/firefox/libxpcom.so -> www-client/firefox |
22 |
> * /usr/lib64/firefox/plugin-container -> www-client/firefox |
23 |
> * /usr/lib64/firefox/sdk/bin/xpcshell -> www-client/firefox |
24 |
> * /usr/lib64/firefox/sdk/lib/libxpcom.so -> www-client/firefox |
25 |
> |
26 |
> The problem seems to be the "no version information available". |
27 |
> revdep-rebuild is now less useful than it should be. |
28 |
> |
29 |
> Has anybody else encountered this problem, and what is the best way to |
30 |
> solve it? |
31 |
> |
32 |
|
33 |
Same problem here, although with V18.0-r1. I have |
34 |
net-libs/xulrunner-2.0.1-r1 on my machine, referring to |
35 |
Jean-Christophe's proposed fix. I'll kill this off with emerge -C and |
36 |
see what happens. |
37 |
|
38 |
Andrew |