[PyKDE] Compliing PyQt under Solaris

Phil Thompson phil at river-bank.demon.co.uk
Fri Oct 12 15:09:28 BST 2001


Matt Francis wrote:
> 
> I'm compiling PyQt-2.5 under Solaris 5.8, using SIP 2.5 and QT 2.3.1.
> I've compiled SIP and QT with g++ version 2.95.3 20010315 (release).
> Compiling PyQt, I get the following error:
> 
> 
> g++ -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/include/python2.1
> -I/usr/include/sip -I/usr/qt/include -I/usr/openwin/include
> -fno-exceptions -O2 -c qtcmodule.cpp  -fPIC -DPIC -o qtcmodule.lo
> In file included from /usr/qt/include/qobjectdefs.h:42,
>                  from /usr/qt/include/qobject.h:42,
>                  from /usr/include/sip/sipQt.h:10,
>                  from sipqtDeclqt.h:40,
>                  from qtcmodule.cpp:33:
> /usr/qt/include/qglobal.h:629: declaration of C function `void
> qObsolete(const char *, const char *)' conflicts with
> /usr/qt/include/qglobal.h:628: previous declaration `void
> qObsolete(const char *, const char *, const char *)' here
> /usr/qt/include/qglobal.h:630: declaration of C function `void
> qObsolete(const char *)' conflicts with
> /usr/qt/include/qglobal.h:629: previous declaration `void
> qObsolete(const char *, const char *)' here
> 
> ...among others.  What gives?  Any ideas?

As PyQt doesn't make any reference to qObsolete this has to be a
difference in the way PyQt is built vs the way Qt is built. For example,
when Qt was built was "-DQT_REJECT_OBSOLETE" passed to g++?

Phil




More information about the PyQt mailing list