[PyKDE] Segmentation faults with PyQt

[Ingo Krabbe]

It is likely that your segFault in PyQt has another reason than PyQt
itself when you don't hear from anywhere else.

What do you call when you get a segFault ?

What's about SIP for example. It is mentioned that SIP 3.4 is also
needed by PyQt 3.4.  You may have some older version lying around, which
should be removed further.

Remeber that the SIP library may live in PYDIR or in /usr/lib or
/usr/local/lib for older versions, which might need to be delted by
hand (I've read this somewhere in SIP Docs).

On Sun, Sep 29, 2002 at 11:03:28AM +0200, Boudewijn Rempt wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> I'm having no end of trouble getting the latest version of PyQt (3.4) to run: 
> both the source from riverbank, as the rpm's from sourceforge cause 
> segmentation faults, even with the included scripts.
> 
> It's frustrating because I see little else than the mere mention of a 
> segmentation fault.
> 
> I've tried Qt 3.0.4, 3.0.5, Python 2.1 and 2.2, SuSE 7.3 and SuSE 8.0 -- now 
> I'm going to try the snapshots of PyQt.
> - -- 
> Boudewijn Rempt | http://www.valdyas.org
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.6 (GNU/Linux)
> Comment: For info see http://www.gnupg.org
> 
> iD8DBQE9lsHidaCcgCmN5d8RAkKTAJ9EtGrB0GgNVFcC5TMvwj4ozZidxgCfdQd0
> c+hxIf4DVeR+ZLSjIPCqNnw=
> =NAFL
> -----END PGP SIGNATURE-----
> 
> _______________________________________________
> PyKDE mailing list    PyKDE at mats.gmd.de
> http://mats.gmd.de/mailman/listinfo/pykde
>