| 1 |
On Monday 22 May 2017 09:49:01 Jörg Schaible wrote: |
| 2 |
> Hi Peter, |
| 3 |
> |
| 4 |
> Peter Humphrey wrote: |
| 5 |
> |
| 6 |
> [snip] |
| 7 |
> |
| 8 |
> > Have you seen https://bugs.gentoo.org/show_bug.cgi?id=595618 ? It says |
| 9 |
> > that "Qt plugins compiled with gcc-4 are incompatible with |
| 10 |
> > <dev-qt/qtcore-4.8.7 compiled with gcc-5." I don't see how portage can |
| 11 |
> > be |
| 12 |
> > expected to anticipate that. On the other hand, some kind of notice |
| 13 |
> > could |
| 14 |
> > be issued, and bug 618922 is pursuing that. (That's the one I started |
| 15 |
> > this thread with.) |
| 16 |
> |
| 17 |
> well, this does not seem to be the complete truth. When I switched to gcc |
| 18 |
> 5.x I did a revdep-rebuild for anything that was compiled against |
| 19 |
> libstdc++.so.6 just like the according news entry was recommending. And I |
| 20 |
> am quite sure that those Qt plugins were part of my 515 recompiled |
| 21 |
> packages. |
| 22 |
> |
| 23 |
> Nevertheless, my KDE 4 apps were broken after the update to Qt 4.8.7. |
| 24 |
> Rebuilding anything that was using libQtCore.so.4 solved it, but I fail to |
| 25 |
> see how this is related to the gcc update two weeks ago. |
| 26 |
|
| 27 |
I can only suggest you read bug report 618922 if you haven't already, |
| 28 |
including following its reference to bug 595618. It makes sense to me. |
| 29 |
|
| 30 |
-- |
| 31 |
Regards |
| 32 |
Peter |
Archives