[kde-solaris] CSWqt libqt-mt (v.3.3.3) conflicts with KDE-gcc libqt-mt (v.3.3.4)

Darin Perusich Darin.Perusich at cognigencorp.com
Tue Aug 30 13:47:03 CEST 2005

hi bob,

are you using kde 3.3.1 or 3.4.1? there are 2 QT packages released by 
blastwave, CSWqt and CSWqtgcc. KDE is built against the CSWqtgcc 
package, the both install into /opt/csw/kde_gcc. i'm running 3.3.1 and 
have both of the QT packages installed and am not having any problems.

do you have LD_LIBRARY_PATH set? if you do unset it as it will cause 
problems. we build all blastwave packages so you do not need it set. 
which QT and KDE packages to you have installed, 'pkg-get -c |egrep 
"(kde|qt)" |grep -v "Not installed"'?

submit a bug at http://www.blastwave.org/bugtrack/, you'll need to 
create an account but don't worry you won't get spamed only notified 
about said bug.

i'd also sign up for the blastwave users list and post this message 
there. i know it sounds wierd but this message really belongs on that 
list as this problem is very specific to the blastwave packages.

BobC wrote:
> Hi KDE users-
> But, I experienced a problem I thought I'd let folks know about (with
> a workaround).
> I installed VLC from blastwave after I installed KDE from blastwave
> (and unfortunately walked away from my box for a week on a business
> trip). When I got back and logged in, kded would die and dump core
> every time. After spending many mornings and nights, I finally
> discovered what was happening.
> On startup, kded was using /opt/csw/lib/libqt-mt.so.3 from CSWqt,
> instead of /opt/csw/kde-gcc/lib/libqt-mt.so.3. The
> /opt/csw/lib/libqt-mt.so* libs are symbollically linked to
> /opt/csw/lib/libqt-mt.so.3.3.3 while KDE needed libqt-mt.so.3.3.4 from
> /opt/csw/kde-gcc/lib.
> So it appears there *could* be a package conflict between kde-gcc and
> anything else that needs libraries from CSWqt (that live in
> /opt/csw/lib).
> To fix it, I created appropriate symbolic llinks from the libqt-mt
> libraries in /opt/csw/lib to the libraries in /opt/csw/kde-gcc/lib.
> But, this now breaks my package database and the pkging repository
> (amoung other things), and I have to *assume* libqt-mt.so.3.3.3 is
> fully backward compatible with libqt-mt.so.3.3.4 (which might not be a
> safe assumption), but it appears most of my other apps work from what
> I can tell.
> So my question is, how else could I fix this without breaking my
> packaging, kde-gcc or the other CSW apps that depend on CSWqt out of
> /opt/csw/lib (knowing there are apps that may need both versions of
> qt-mt) ?
> I've thought about submitting this as a bug/package conflict on
> blastwave's bug tracking system if that would help.... anyway, any
> other suggestions about how to more gracefully fix "versioned dynamic
> linking" without recompiling or breaking other apps would be greatly
> appreciated.
> Thanks,
> Bob
> ___________________________________________________
> This message is from the kde-solaris mailing list.
> Account management:  https://mail.kde.org/mailman/listinfo/kde-solaris.
> Archives: http://lists.kde.org/.
> More info: http://www.kde.org/faq.html.

Darin Perusich
Unix Systems Administrator
Cognigen Corp.
darinper at cognigencorp.com

More information about the kde-solaris mailing list