[PyKDE] PyQt fails

[Phil Thompson]

On Tuesday 14 January 2003 6:20 pm, Paul F. Kunz wrote:
> >>>>> On Tue, 14 Jan 2003 18:03:33 +0000, Phil Thompson
> >>>>> <phil at river-bank.demon.co.uk> said:
> >
> > On Tuesday 14 January 2003 5:47 pm, Paul F. Kunz wrote:
> >> On a Red Hat Linux 7.2 system I just built sip-3.5 and PyQt 3.5
> >> with gcc 2.95.3.  I get immediate failure
> >>
> >> [pfkeb at Kunz-pbdsl1 RunControl]$ python Python 2.2.2 (#1, Oct 15
> >> 2002, 07:42:56) [GCC 2.95.3 20010315 (release)] on linux2 Type
> >> "help", "copyright", "credits" or "license" for more information.
> >>
> >> >>> from qt import *
> >>
> >> Traceback (most recent call last): File "<stdin>", line 1, in ?
> >> File "/usr/local/lib/python2.2/site-packages/qt.py", line 39, in ?
> >> import libqtc ImportError:
> >> /usr/local/lib/python2.2/site-packages/libqtcmodule.so: undefined
> >> symbol: metaObject__C16QAssistantClient
> >>
> >> The symbol demangles to `QAssistantClient::metaObject(void) const'
> >>
> >> Any ideas?
> >
> > When you build Qt don't "make install".
>
>    In other words, built Qt in place in for example /usr/local/qt?

Yes.

> That leaves a lot of extra stuff in /usr/local that doesn't need to be
> there.
>
>    Could I take QAssistantClient out of the of the PyQt build?

Yes, by hacking build.py.

There are alternatives that work around the (Qt) bug. Look though the mailing 
list archives.

Phil