| 1 |
On 05/16/2011 02:06 PM, Pau Peris wrote: |
| 2 |
> Hi, does anyone knows how to solve it? |
| 3 |
> Reemerging did nothing |
| 4 |
> |
| 5 |
> ldd -r /usr/lib64/libdbusmenu-qt.so.2 |
| 6 |
|
| 7 |
(snippage) |
| 8 |
> undefined symbol: _ZN5QHashIi15QHashDummyValueE13detach_helperEv (/usr/lib64/libdbusmenu-qt.so.2) |
| 9 |
> undefined symbol: _ZN5QListI7QStringE6appendERKS0_ (/usr/lib64/libdbusmenu-qt.so.2) |
| 10 |
> undefined symbol: _ZN4QMapIP7QActioniE11node_createEP8QMapDataPPNS3_4NodeERKS1_RKi (/usr/lib64/libdbusmenu-qt.so.2) |
| 11 |
(more snippage) |
| 12 |
|
| 13 |
All of the missing symbols are c++ symbols, so I wonder if you |
| 14 |
compiled the qt packages with a different version of gcc. i.e. |
| 15 |
the new dbusmenu library may be linked with a different libstdc++ |
| 16 |
(which is supplied by the gcc package and so you may have more |
| 17 |
than one libstdc++ on your machine). |
| 18 |
|
| 19 |
Any time you switch compilers, you really should rebuild every |
| 20 |
package that requires libstdc++, and that's a lot of packages. |
| 21 |
|
| 22 |
A quick and dirty test would be to re-emerge all the qt packages |
| 23 |
(using the same gcc you're using now) and see if the problem goes |
| 24 |
away. |
Archives