The first bug in the new release turns out to be in the README file. I believe I already posted this info to the list, but I'll repeat it (and update the README) The release is now available on http://riverbankcomputing.co.uk
sip/PyQt currently link to qt-mt if you have it. KDE3 is usually built with qt-mt, so there is no problem there. KDE2 however is built with qt. If you have KDE2 and Qt >= 2.3.1, you will have both qt and qt-mt libs. In that case, PyKDE configure should fail if you built sip/PyQt normally (PyKDE checks for a qt/qt-mt mismatch). The workaround is to hide libqt-mt.* (rename them for instance) when building sip/PyQt/PyKDE. You can restore libqt-mt.* after building. I forgot to include this info in the README. That of course means you can't use Qt threads and PyKDE (for KDE2.x only) at the same time. Also, it appears that PyKDE now builds successfully with gcc2.96, which affects RH and Mandrake 8.2 users. Let me know if that isn't correct. Thanks to Bill Soudan for RH testing and info. Now I can return to deleting Korean spam and Klez-infested emails. (Out of 185 emails this morning, all but 30 were spam or virus-generated. Arghhh!). Jim _______________________________________________ PyKDE mailing list [EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde