1 |
On 06/29/2009 08:04 AM, Roy Wright wrote: |
2 |
> On ~x86 did the upgrade to qt 4.5.2 and get the following message: |
3 |
> |
4 |
> "After a rebuild or upgrade of Qt, it can happen that Qt plugins (such |
5 |
> as Qt |
6 |
> and KDE styles and widgets) can no longer be loaded. In this situation you |
7 |
> should recompile the packages providing these plugins... |
8 |
> |
9 |
> "Packages that typically need to be recompiled are kdelibs from KDE4, any |
10 |
> additional KDE4/Qt4 styles, qscintilla and PyQt4..." |
11 |
> |
12 |
> Then followed the link on the plugins which stated: |
13 |
> |
14 |
> "The Qt library and all plugins are built using a build key. The build |
15 |
> key in the Qt library is examined against the build key in the plugin, |
16 |
> and if they match, the plugin is loaded. If the build keys do not match, |
17 |
> then the Qt library refuses to load the plugin." |
18 |
> |
19 |
> So how do I find all the installed qt plugins on my system and check |
20 |
> their build keys? |
21 |
|
22 |
You can obtain a list of packages that might depend upon any Qt 4 |
23 |
package with: |
24 |
|
25 |
for p in `qlist -IC x11-libs/qt:4`; do equery -q depends "$p"; done | |
26 |
sort | uniq |
27 |
|
28 |
This command can take several minutes to complete. Of course not every |
29 |
one of those packages needs to be rebuilt, but it makes it easier to |
30 |
pick some by hand. Usually though, it's not necessary to rebuild |
31 |
anything, especially during minor updates (like from Qt 4.5.1 to 4.5.2). |