[PyQt] QML problems when building PyQt-5.1.1

Phil Thompson phil at riverbankcomputing.com
Sun Nov 10 17:24:34 GMT 2013


On Sat, 9 Nov 2013 11:05:33 -0500, Darren Dale <dsdale24 at gmail.com> wrote:
> Good morning,
> 
> I'm building PyQt-5.1.1 using sip-4.15.3 on Scientific Linux 6.4. I
> installed qt-5.1.1 with yum (provided by the EPEL repository), and was
> able to build PyQt5 if I just had only qtbase installed.
> 
> But if I try to build PyQt5 when the rest of the qt5 split packages
> are installed, I get errors:
> 
> g++ -c -m64 -pipe -fno-strict-aliasing -O2 -g -pipe -Wall
> -Wp,-D_FORTIFY_SOURCE=2 -fstack-protector --param=ssp-buffer-size=4
> -m64 -mtune=generic -O2 -fPIC -Wall -W -D_REENTRANT -DQT_NO_DEBUG
> -DQT_CORE_LIB -I/usr/lib64/qt5/mkspecs/linux-g++-64 -I. -I.
> -I../../QtCore -I/usr/local/lib64/anaconda/envs/py3k/include/python3.3m
> -I/usr/include/qt5 -I/usr/include/qt5/QtCore -I. -o
> qpycore_qstringlist.o qpycore_qstringlist.cpp
> In file included from qpycore_pyqtconfigure.cpp:29:
> qpycore_pyqtboundsignal.h:37: warning: declaration ‘class
> Chimera::Signature’ does not declare anything
> g++ -c -m64 -pipe -fno-strict-aliasing -O2 -g -pipe -Wall
> -Wp,-D_FORTIFY_SOURCE=2 -fstack-protector --param=ssp-buffer-size=4
> -m64 -mtune=generic -O2 -fPIC -Wall -W -D_REENTRANT -DQT_NO_DEBUG
> -DQT_CORE_LIB -I/usr/lib64/qt5/mkspecs/linux-g++-64 -I. -I.
> -I../../QtCore -I/usr/local/lib64/anaconda/envs/py3k/include/python3.3m
> -I/usr/include/qt5 -I/usr/include/qt5/QtCore -I. -o qpycore_types.o
> qpycore_types.cpp
> g++ -c -m64 -pipe -fno-strict-aliasing -O2 -g -pipe -Wall
> -Wp,-D_FORTIFY_SOURCE=2 -fstack-protector --param=ssp-buffer-size=4
> -m64 -mtune=generic -O2 -fPIC -Wall -W -D_REENTRANT -DQT_NO_DEBUG
> -DQT_CORE_LIB -I/usr/lib64/qt5/mkspecs/linux-g++-64 -I. -I.
> -I../../QtCore -I/usr/local/lib64/anaconda/envs/py3k/include/python3.3m
> -I/usr/include/qt5 -I/usr/include/qt5/QtCore -I. -o qpycore_qvariant.o
> qpycore_qvariant.cpp
> In file included from qpycore_pyqtsignal.cpp:29:
> qpycore_pyqtboundsignal.h:37: warning: declaration ‘class
> Chimera::Signature’ does not declare anything
> g++ -c -m64 -pipe -fno-strict-aliasing -O2 -g -pipe -Wall
> -Wp,-D_FORTIFY_SOURCE=2 -fstack-protector --param=ssp-buffer-size=4
> -m64 -mtune=generic -O2 -fPIC -Wall -W -D_REENTRANT -DQT_NO_DEBUG
> -DQT_CORE_LIB -I/usr/lib64/qt5/mkspecs/linux-g++-64 -I. -I.
> -I../../QtCore -I/usr/local/lib64/anaconda/envs/py3k/include/python3.3m
> -I/usr/include/qt5 -I/usr/include/qt5/QtCore -I. -o
> qpycore_qvariant_value.o qpycore_qvariant_value.cpp
> In file included from qpycore_qobject_getattr.cpp:28:
> qpycore_pyqtboundsignal.h:37: warning: declaration ‘class
> Chimera::Signature’ does not declare anything
> In file included from qpycore_qobject_helpers.cpp:31:
> qpycore_pyqtboundsignal.h:37: warning: declaration ‘class
> Chimera::Signature’ does not declare anything
> rm -f libqpycore.a
> ar cqs libqpycore.a qpycore_chimera.o qpycore_chimera_signature.o
> qpycore_chimera_storage.o qpycore_classinfo.o qpycore_decorators.o
> qpycore_init.o qpycore_misc.o qpycore_post_init.o qpycore_public_api.o
> qpycore_pyqtboundsignal.o qpycore_pyqtconfigure.o
> qpycore_pyqtmethodproxy.o qpycore_pyqtproperty.o
> qpycore_pyqtpyobject.o qpycore_pyqtsignal.o qpycore_pyqtslot.o
> qpycore_pyqtslotproxy.o qpycore_qmessagelogger.o qpycore_qmetaobject.o
> qpycore_qmetaobject_helpers.o qpycore_qobject_getattr.o
> qpycore_qobject_helpers.o qpycore_qstring.o qpycore_qstringlist.o
> qpycore_types.o qpycore_qvariant.o qpycore_qvariant_value.o
> make[2]: Leaving directory
> `/home/darren/Downloads/PyQt-gpl-5.1.1/qpy/QtCore'
> rm -f libqpyquick.a
> ar cqs libqpyquick.a qpyquick_post_init.o qpyquick_chimera_helpers.o
> qpyquick_register_type.o qpyquickitem.o qpyquickpainteditem.o
> make[2]: Leaving directory
> `/home/darren/Downloads/PyQt-gpl-5.1.1/qpy/QtQuick'
> make[1]: Leaving directory `/home/darren/Downloads/PyQt-gpl-5.1.1/qpy'
> make: *** [sub-qpy-make_first-ordered] Error 2

I don't see how the above can be the output of a fresh source tree.

> If I comment out the references to QtQML on lines 82, 131, and 968,
> then I can get PyQt5 to build again. Any suggestions what may be
> wrong?

In case it's an old GCC you could try the current PyQt snapshot.

Phil


More information about the PyQt mailing list