trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: March 2011

Re: [trinity-devel] PyKDE3 FTBFS: cannot find -lDCOP

From: Darrell Anderson <humanreadable@...>
Date: Thu, 24 Mar 2011 22:23:47 -0700 (PDT)
Hey folks, would appreciate some help with this. :)

I no longer can compile 3.5.12 in the same system I built the packages last autumn. :(

Here is the build log.

========================================================================
Prepping for a clean build...

Start time: 2011-03-25 00:08:21

Building pykde3-3.16.7-i486-1.tgz.

Package will be stored at /home/public/builds/slackware/kde-3.5.x.

Unpacking pykde3-3.16.7 source files to /dev/shm...
Finished unpacking.

Running ./configure.py -k /opt/trinity -L /opt/trinity/lib -n /opt/trinity/lib/kde3 -o /opt/trinity/include -i
Please be patient.

     PyKDE version 3.16.6
           -------

Python include directory is /usr/include/python2.5
Python version is 2.5.2

sip version is 4.11.1 (4.11.1)

Qt directory is /usr/lib/qt-3.3.8c
Qt version is 3.3.8

PyQt directory is /usr/share/sip
PyQt version is 3.18.1 (3.18.1)

gcc version 4.2.4
no concatenation

KDE base directory is /opt/trinity
KDE include directory is /opt/trinity/include
KDE lib directory is /opt/trinity/lib/kde3
lib directory is /opt/trinity/lib

*** True KDE version is 0x3050c -- building for KDE 0x30503 ***

KDE version is 3.5.3 (0x30503)

PyKDE modules will be installed in /usr/lib/python2.5/site-packages
PyKDE .sip files will be installed in /usr/share/sip

PyKDE modules to be built:
   dcop kdecore kdefx kdeui kio kresources kabc kutils kfile kparts khtml kspell kdeprint kmdi

Generating the C++ source for the dcop module...
Creating the Makefile for the dcop module...

Generating the C++ source for the kdecore module...
Creating the Makefile for the kdecore module...

Generating the C++ source for the kdefx module...
Creating the Makefile for the kdefx module...

Generating the C++ source for the kdeui module...
Creating the Makefile for the kdeui module...

Generating the C++ source for the kio module...
Creating the Makefile for the kio module...

Generating the C++ source for the kresources module...
Creating the Makefile for the kresources module...

Generating the C++ source for the kabc module...
Creating the Makefile for the kabc module...

Generating the C++ source for the kutils module...
Creating the Makefile for the kutils module...

Generating the C++ source for the kfile module...
Creating the Makefile for the kfile module...

Generating the C++ source for the kparts module...
Creating the Makefile for the kparts module...

Generating the C++ source for the khtml module...
Creating the Makefile for the khtml module...

Generating the C++ source for the kspell module...
Creating the Makefile for the kspell module...

Generating the C++ source for the kdeprint module...
Creating the Makefile for the kdeprint module...

Generating the C++ source for the kmdi module...
Creating the Makefile for the kmdi module...

Creating top level Makefile...
Creating pykdeconfig.py...
make[1]: Entering directory `/dev/shm/PyKDE-3.16.7/dcop'
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-3.3.8c/mkspecs/default -I/usr/lib/qt-3.3.8c/include -I/usr/X11R6/include -o sipdcopcmodule.o sipdcopcmodule.cpp
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-3.3.8c/mkspecs/default -I/usr/lib/qt-3.3.8c/include -I/usr/X11R6/include -o sipdcopQPtrList0100DCOPObject.o sipdcopQPtrList0100DCOPObject.cpp
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-3.3.8c/mkspecs/default -I/usr/lib/qt-3.3.8c/include -I/usr/X11R6/include -o sipdcopQValueList0100QCString.o sipdcopQValueList0100QCString.cpp
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-3.3.8c/mkspecs/default -I/usr/lib/qt-3.3.8c/include -I/usr/X11R6/include -o sipdcopDCOPStub.o sipdcopDCOPStub.cpp
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-3.3.8c/mkspecs/default -I/usr/lib/qt-3.3.8c/include -I/usr/X11R6/include -o sipdcopDCOPRef.o sipdcopDCOPRef.cpp
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-3.3.8c/mkspecs/default -I/usr/lib/qt-3.3.8c/include -I/usr/X11R6/include -o sipdcopDCOPReply.o sipdcopDCOPReply.cpp
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-3.3.8c/mkspecs/default -I/usr/lib/qt-3.3.8c/include -I/usr/X11R6/include -o sipdcopDCOPObjectProxy.o sipdcopDCOPObjectProxy.cpp
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-3.3.8c/mkspecs/default -I/usr/lib/qt-3.3.8c/include -I/usr/X11R6/include -o sipdcopDCOPObject.o sipdcopDCOPObject.cpp
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-3.3.8c/mkspecs/default -I/usr/lib/qt-3.3.8c/include -I/usr/X11R6/include -o sipdcopDCOPClient.o sipdcopDCOPClient.cpp
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-3.3.8c/mkspecs/default -I/usr/lib/qt-3.3.8c/include -I/usr/X11R6/include -o sipdcopDCOPClientTransaction.o sipdcopDCOPClientTransaction.cpp
g++ -shared -Wl,-rpath,/opt/trinity/lib/kde3 -Wl,-rpath,/usr/lib/qt-3.3.8c/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-3.3.8c/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
========================================================================


Darrell


--- On Sun, 3/20/11, Darrell Anderson <humanreadable@...> wrote:

> From: Darrell Anderson <humanreadable@...>
> Subject: [trinity-devel] PyKDE3 FTBFS: cannot find -lDCOP
> To: trinity-devel@...
> Date: Sunday, March 20, 2011, 12:49 PM
> 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
> 
> 
>       
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: trinity-devel-unsubscribe@...
> For additional commands, e-mail: trinity-devel-help@...
> Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/
> Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
> 
>