[PyKDE] Problems compiling PyKDE

Jonathan Gardner jgardner at jonathangardner.net
Mon Aug 11 16:52:00 BST 2003


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Saturday 09 August 2003 19:07, Jim Bublitz wrote:
> On Saturday August 9 2003 17:46, Peter Clark wrote:
> > On Saturday 09 August 2003 07:41 pm, Jonathan Gardner wrote:
> > > g++ -shared -Wl,-soname,libkdecorecmodule.so.1 -o
> > > libkdecorecmodule.so.1.0.0 kdecorehuge.o
> > > moc_sipkdecoreProxykdecore.o -L/usr/lib/qt-3.1/lib
> > > -L/usr/X11R6/lib -L/usr/lib/python2.2/site-packages
> > > -L/usr/lib -lsip -lqtcmodule -lDCOP -lkdecore -ldcopcmodule
> > > -lqt-mt -lXext -lX11 -lm -lpthread
> > > /usr/bin/ld: cannot find -ldcopcmodule
> > > collect2: ld returned 1 exit status
> > >
> > > It can't seem to find the dcopcmodule.
> >
> > 	Assuming that you have the C bindings for DCOP, try running
> > 'make' as root. I had the same problem when I first tried to
> > compile it, but then I read the README, which explains that
> > _both_ building and installation need to be done as root.
>
> Sounds right - you need to be root to put libdcopcmodule into
> /site-packages. If you're not, it won't get there and won't be
> found by kdecore when it tries to link.
>

I've thought about this for a while over the weekend. I think what you are 
saying is right. I apologize to Peter for blowing him off so quickly -- he 
was correct.

When I build the PyKDE RPM, I have to put everything into a temporary file 
structure. That means that I expected PyKDE to put it's modules into that 
tree. I'll take a look at it when I get home, and make some modifications to 
build.py so I can use it to make an RPM.

- -- 
Jonathan Gardner <jgardner at jonathangardner.net>
Live Free, Use Linux!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE/N61IWgwF3QvpWNwRAod9AJ9+RiW5Moxj3ISr5HURYGx/SRc7UgCg3Vsc
8m37cx4D9iYXGJ87bjP/8q8=
=AvC6
-----END PGP SIGNATURE-----




More information about the PyQt mailing list