New subject: [trinity-devel] PyKDE3 FTBFS: cannot find -lDCOP

20 Mar 2011

Here is the end of the build log:

===========================================
g++ -c -Wno-deprecated-declarations -pipe -fPIC -O2 -Wall -W -D_REENTRANT -DNDEBUG
-DQT_NO_DEBUG -DQT_THREAD_SUPPORT -I. -I../extra/kde353 -I/opt/trinity/include
-I/usr/include/python2.5 -I/usr/lib/qt/mkspecs/default -I/usr/lib/qt/include
-I/usr/X11R6/include -o sipdcopDCOPClientTransaction.o sipdcopDCOPClientTransaction.cpp
g++ -shared -Wl,-rpath,/opt/trinity/lib/kde3 -Wl,-rpath,/usr/lib/qt/lib
-Wl,--version-script=dcop.exp -o dcop.so sipdcopcmodule.o sipdcopQPtrList0100DCOPObject.o
sipdcopQValueList0100QCString.o sipdcopDCOPStub.o sipdcopDCOPRef.o sipdcopDCOPReply.o
sipdcopDCOPObjectProxy.o sipdcopDCOPObject.o sipdcopDCOPClient.o
sipdcopDCOPClientTransaction.o -L/opt/trinity/lib/kde3 -L/usr/lib/qt/lib -L/usr/X11R6/lib
-lDCOP -lqt-mt -lXext -lX11 -lm -lpthread
/usr/lib/gcc/i486-slackware-linux/4.2.4/../../../../i486-slackware-linux/bin/ld: cannot
find -lDCOP
collect2: ld returned 1 exit status
make[1]: *** [dcop.so] Error 1
make[1]: Leaving directory `/dev/shm/PyKDE-3.16.7/dcop'
make: *** [all] Error 2
===========================================

I'm progressing my way toward building Trinity on the most recent Slackware release.
For preparation, I am first building Trinity on Slackware 12.2 using the 3.5.12 tarballs.
The idea is that Trinity 3.5.12 will get installed and coexist with KDE 3.5.10. When I
eliminate the building bugs I then will start building on the latest Slackware release,
where QT4 and KDE4 is installed.

I can build 3.5.12 on Slackware 12.2. That was with an installation location in the
traditional /usr rather than /opt/trinity.

I built the four 3.5.12 core packages using $PREFIX=/opt/trinity. I built sip and PyQT3
without errors.

The next package in the build sequence before building kdebindings with python support is
PyKDE3. I'm building PyKDE3 with the following:

python ./configure.py -k $PREFIX -L $LIBDIR -n $LIBDIR/kde3 -o $PREFIX/include -i

where:

KDE base directory ($PREFIX): /opt/trinity
lib directory ($LIBDIR): /opt/trinity/lib
KDE lib directory: /opt/trinity/lib/kde3
KDE include directory: /opt/trinity/include

PyKDE3 built fine when I used the original locations of /usr, /usr/include, /usr/lib,
/usr/lib/kde3.

I built and installed sip and pyqt3 to /usr rather than /opt/trinity as there is no
conflict with other packages that I know. When PyKDE3 FTBFS, I then rebuilt those two
packages to install in /opt/trinity.

Same failure.

Probably a path problem. Any ideas?

Darrell