[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: 3.1 Branch - compile problems on SUSE SLES8 - is this a
From:       Ferdinand  Gassauer <f.gassauer () aon ! at>
Date:       2003-08-06 6:26:49
[Download RAW message or body]

On Monday 04 August 2003 21:59, Ferdinand Gassauer wrote:
> On Monday 04 August 2003 21:39, Ferdinand Gassauer wrote:
> > On Monday 04 August 2003 19:18, Ferdinand Gassauer wrote:
> > > On Monday 04 August 2003 18:49, Thiago Macieira wrote:
> > > > Ferdinand Gassauer wrote:
> > > > >Hi!
> > > > >I tried to compile qt 3.1.2, arts 1.1.3 and KDE 3.1 branch (cvs) on
> > > > > suse sles8 with gcc-3.2.2-5 (because of oracle)
> > > > > /daten/download/src/kdecvs/kdelibs/kdefx/.libs/ libkdefx.so.4:
> > > > > undefined symbol:
> > > > >_ZN18QMetaObjectCleanUpC1EPKcPFP11QMetaObjectvE
> > > >
> > > > This probably means you have more than libqt-mt.so.3 in your system.
> > > > It could also mean that you had a newer version of Qt and some
> > > > libraries that are being used were compiled against it.
> > >
> > > yes I have 2 more libqt-mt.so.3
> > > but
> > > as I have set QTDIR correctly (at least configure points to the right
> > > directories)
> > > I do not know why it does not   work
> >
> > my settings
> > export QTDIR=`pwd`/qt-copy
> > echo $QTDIR
> > export KDEDIR=/daten/download/kde31
> > echo $KDEDIR
> > export PATH=$QTDIR/bin:$PATH
> > LD_LIBRARY_PATH=$KDEDIR/lib:$QTDIR/lib
> > LD_RUN_PATH=$KDEDIR/lib:$QTDIR/lib
> > export LD_LIBRARY_PATH LD_RUN_PATH
> > QT_LIB=$QTDIR/lib
> > QT_INCL=$QTDIR/include
> > export QT_LIB QT_INCL
> >
> > can it be that a KDE script does not point to the rigth location ? How
> > can I check?
>
> after removing the 3.0.5 libqt-mt.so.3 it compiles
> but still I wonder why it does not take the files form $QTDIR.

I had to 
export LD_PRELOAD=<path_to_my_special_qt3>/libqt-mt.so.3
compilation works now, but very slow (obviously ?)

but also at runtime I have to set this variable. here I do not notice a 
slowdown of loading

any idea where this strange behaviour comes from , I mean that the standard qt  
library takes precedence over whatever I specified.

-- 
mit freundlichen Grüßen
Ferdinand Gassauer
Tel. +43(1)7122194

 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

[prev in list] [next in list] [prev in thread] [next in thread]