Bugzilla – Bug 1125542
[Build 20190214] python-qt4 build failure stops zdup process
Last modified: 2019-03-01 19:40:58 UTC
## Observation openQA test in scenario opensuse-Tumbleweed-NET-x86_64-zdup-13.2@64bit fails in [zdup](https://openq ## Test suite description ## Reproducible Fails since (at least) Build [20190202](https://openqa.opensuse.org/tests/845590) ## Expected result Last good: [20190201](https://openqa.opensuse.org/tests/845046) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?test=zdup-13.2&arch=x86_64&version=Tumbleweed&flavor=NET&distri=opensuse&machine=64bit) The root cause for this openQA failure is python-qt4 build failure after the upgrade of python-sip.
[ 111s] g++ -c -pipe -fno-exceptions -g -Wall -W -D_REENTRANT -fPIC -DSIP_PROTECTED_IS_PUBLIC -Dprotected=public -DQT_PLUGIN -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/default -I. -I/usr/include/QtCore -I/usr/include -I. -I/usr/include/python2.7 -I../../qpy/QtCore -I. -o sipQtCoreQAbstractItemModel.o sipQtCoreQAbstractItemModel.cpp [ 113s] /home/abuild/rpmbuild/BUILD/PyQt4_gpl_x11-4.12.3/build_2.7/QtCore/sipQtCoreQAbstractAnimation.cpp:1076:1: error: cannot convert 'std::nullptr_t' to 'int' in initialization [ 113s] }; [ 113s] ^ [ 113s] /home/abuild/rpmbuild/BUILD/PyQt4_gpl_x11-4.12.3/build_2.7/QtCore/sipQtCoreQAbstractEventDispatcher.cpp:1167:1: error: cannot convert 'std::nullptr_t' to 'int' in initialization [ 113s] sipNameNr_QAbstractEventDispatcher, [ 113s] ^ [ 113s] /home/abuild/rpmbuild/BUILD/PyQt4_gpl_x11-4.12.3/build_2.7/QtCore/sipQtCoreQAbstractItemModel.cpp:3036:1: error: cannot convert 'std::nullptr_t' to 'int' in initialization [ 113s] SIP_NULLPTR, [ 113s] ^
*** Bug 1125636 has been marked as a duplicate of this bug. ***
JFYI, I managed to build python-qt4 by adding "-std=c++98" to the compiler flags. I.e. something like: diff -u a/configure-ng.py b/configure-ng.py --- a/configure-ng.py +++ b/configure-ng.py @@ -2400,7 +2400,7 @@ spec = 'macx-g++' if 'g++' in spec or 'clang' in spec: - pro_lines.append('QMAKE_CXXFLAGS += -fno-exceptions') + pro_lines.append('QMAKE_CXXFLAGS += -fno-exceptions -std=c++98') # This optimisation could apply to other platforms. if 'linux' in spec and not target_config.static: That would IME make it necessary to compile all depending packages with "-std-c++98" as well though (because the generated code requires it), so not a proper fix I think.
*** Bug 1125691 has been marked as a duplicate of this bug. ***
This is still outstanding and has now hit tumbleweed 4 Problems: Problem: python2-qt4-4.12.3-1.3.x86_64 requires python2-sip(api) = 12.5, but this requirement cannot be provided Problem: python3-qt4-4.12.3-1.3.x86_64 requires python3-sip(api) = 12.5, but this requirement cannot be provided Problem: python2-sip-4.19.13-2.3.x86_64 requires python2-sip-common = 4.19.13, but this requirement cannot be provided Problem: python3-qt4-4.12.3-1.3.x86_64 requires python3-sip(api) = 12.5, but this requirement cannot be provided
A fix (from upstream) is on the way to Tumbleweed: https://build.opensuse.org/request/show/678047
(In reply to Wolfgang Bauer from comment #6) > A fix (from upstream) is on the way to Tumbleweed: > https://build.opensuse.org/request/show/678047 Works for me. Thx.
and works for me, tks
*** Bug 1127435 has been marked as a duplicate of this bug. ***
The updated python-sip is in Factory since yesterday, but python-qt4 has not been rebuilt yet. It would probably need a manual trigger...
python-qt4 built successfully in Factory meanwhile, and the "zdup" test passed as well again: https://openqa.opensuse.org/tests/865963 So I'll close this. The conflict should be gone in the next TW snapshot.