Hello all,
I've decided to try out KDE 4.2. I unmasked all the packages that I
needed, but when I was emerging kde-base/ksysguard I got the following
error:
Linking CXX shared library ../../lib/libkdeinit4_ksysguard.so
[ 98%] Built target kdeinit_ksysguard
Scanning dependencies of target ksysguar
2009/1/28 Tomas Linhart
> Hello all,
>
> I've decided to try out KDE 4.2. I unmasked all the packages that I
> needed, but when I was emerging kde-base/ksysguard I got the following
> error:
>
> Linking CXX shared library ../../lib/libkdeinit4_ksysguard.so
> [ 98%] Built target kdeinit_ksysguard
2009/1/29 Nick Cunningham :
>
>
> Some basic info like emerge --info (or paludis equivilant) would be a good
> start, likewise confirming that the build still fails with portage would
> also be useful (im not saying anything about paludis before any flamewars
> start, just wanting to rule out the p
On Mittwoch 28 Januar 2009, Tomas Linhart wrote:
> Hello all,
>
> I've decided to try out KDE 4.2. I unmasked all the packages that I
> needed, but when I was emerging kde-base/ksysguard I got the following
> error:
>
> Linking CXX shared library ../../lib/libkdeinit4_ksysguard.so
> [ 98%] Built ta
2009/1/29 Volker Armin Hemmann :
>>
>> I tried to re-emerge qt-* packages but the error remains the same.
>>
>> Does somebody have a idea what could be wrong?
>
> re-emerge the qt packages in the right order.
> then emerge kdelibs again, then the rest. Stuff like this happens when qt is
> updated a
On Thu, Jan 29, 2009 at 10:03 AM, Tomas Linhart wrote:
> 2009/1/29 Volker Armin Hemmann :
>>
>> re-emerge the qt packages in the right order.
>> then emerge kdelibs again, then the rest. Stuff like this happens when qt is
>> updated after kdelibs is built against it.
>>
>
> Thanks for your answer.
On Donnerstag 29 Januar 2009, Tomas Linhart wrote:
> Before I start again - what is "the right order" for emerging the qt
> packages?
I am not sure anymore - if you look into the ebuilds you should be able to see
it.
On Donnerstag 29 Januar 2009, Tomas Linhart wrote:
> Before I start again - what is "the right order" for emerging the qt
> packages?
I am not sure anymore - if you look into the ebuilds you should be able to see
it.
Everything is going fine now. The problem was that
/usr/lib64/qt4/libQtWebKit.so.4 was symlinked to QtWebkit 4.5 library
and that was the reason why some symbols could not be found. After
correcting the symlink the problem disappeared.
However, it seems strange to me, because I have tried and later
Volker Armin Hemmann wrote:
> On Donnerstag 29 Januar 2009, Tomas Linhart wrote:
>
>
>> Before I start again - what is "the right order" for emerging the qt
>> packages?
>>
>
> I am not sure anymore - if you look into the ebuilds you should be able to
> see
> it.
>
>
>
I would --onesh
10 matches
Mail list logo
