1 |
Hello Kai, |
2 |
|
3 |
Kai Krakow wrote: |
4 |
|
5 |
> Am Mon, 22 May 2017 19:33:55 +0200 |
6 |
> schrieb Jörg Schaible <joerg.schaible@×××.de>: |
7 |
> |
8 |
>> Peter Humphrey wrote: |
9 |
|
10 |
[snip] |
11 |
|
12 |
>> > |
13 |
>> > I can only suggest you read bug report 618922 if you haven't |
14 |
>> > already, including following its reference to bug 595618. It makes |
15 |
>> > sense to me. |
16 |
>> |
17 |
>> It does not for me. My packages were already compiled with gcc-5.4.0. |
18 |
>> Those Buzilla issues only talk about (plasma/qt) packages compiled |
19 |
>> with previous gcc-4.x which are supposed to be incompatible. All of |
20 |
>> the plasma/qt related packages that have been recompiled, because |
21 |
>> they were built upon libQtCore.so.4 were already recompiled with |
22 |
>> gcc5. I've checked my logs. |
23 |
> |
24 |
> Is the problem maybe order of building packages? |
25 |
> |
26 |
> From your description I see one edge case: Plasma could have been |
27 |
> compiled with gcc-5 but linked to qt still built with gcc-4. Then, qt |
28 |
> was rebuilt after this and is compiled by gcc-5 now. |
29 |
> |
30 |
> Without reading the bug report I would guess that is what the bug is |
31 |
> about: Linking plasma against gcc-4 built qt binaries... Even when you |
32 |
> rebuild qt with gcc-5 after this, you'd need to relink plasma. |
33 |
> |
34 |
> From your logs, you should see the order in which those packages were |
35 |
> rebuilt and linked. |
36 |
> |
37 |
> revdep-rebuild is not always able to perfectly order packages right for |
38 |
> emerge, and emerge in turn has no problem with wrong ordering because |
39 |
> it is rebuilding packages and the dependency constraints are already |
40 |
> fulfilled (read: runtime and build deps are already there). Portage |
41 |
> does not consider rebuilds as a hard dependency/precondition for |
42 |
> rebuilding other packages... |
43 |
> |
44 |
> As far as I understood, "--changed-deps" should fix this and also |
45 |
> rebuild packages depending on the rebuilt packages _after_ they've been |
46 |
> rebuilt. |
47 |
> |
48 |
> The "--empty" option would have a similar effect, tho rebuild many more |
49 |
> packages. |
50 |
> |
51 |
> You could've tried if "revdep-rebuild ... -- --changed-deps" would've |
52 |
> done anything better. I would be interested... |
53 |
|
54 |
Too late now for this, but your assumption can be true. The rebuild for the |
55 |
gcc5 switch did not work smoothly because emerge failed to build all 515 |
56 |
packages reported by revdep-rebuild in correct order. Especially the Kontact |
57 |
suite was affected, because emerge tried to build kdepim-common-libs before |
58 |
some of the dependent packages (happened to me on two different machines). A |
59 |
second run rebuilding only the failed stuff succeeded in the end, but that |
60 |
might have lead to the linker situation you've described above. I wonder, |
61 |
what else might still be affected :-/ |
62 |
|
63 |
Cheers, |
64 |
Jörg |