View previous topic :: View next topic |
Author |
Message |
STrRedWolf n00b
Joined: 02 Sep 2002 Posts: 72
|
Posted: Sat Dec 31, 2016 3:12 pm Post subject: dev-python/PyQT4-4.11.4-r1 breaks on rebuild after new sip |
|
|
Ran my weekly "emerge --sync/emerge -avDuN world" update... and dev-python/PyQT4 broke on rebuild.
Code: | x86_64-pc-linux-gnu-g++ -c -march=core-avx2 -O2 -pipe -fno-exceptions -Wall -W -D_REENTRANT -fPIC -DSIP_PROTECTED_IS_PUBLIC -Dprotected=public -DQT_NO_DEBUG -DQT_PLUGIN -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++ -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4 -I. -I/usr/include/python2.7 -I../../PyQt-x11-gpl-4.11.4/qpy/QtCore -I. -o qpycore_types.o ../../PyQt-x11-gpl-4.11.4/qpy/QtCore/qpycore_types.cpp
../../PyQt-x11-gpl-4.11.4/qpy/QtCore/qpycore_types.cpp: In function ‘int pyqtWrapperType_init(pyqtWrapperType*, PyObject*, PyObject*)’:
../../PyQt-x11-gpl-4.11.4/qpy/QtCore/qpycore_types.cpp:156:5: error: ‘pyqt4ClassTypeDef’ was not declared in this scope
pyqt4ClassTypeDef *pyqt_td = (pyqt4ClassTypeDef *)((sipWrapperType *)self)->type;
^
../../PyQt-x11-gpl-4.11.4/qpy/QtCore/qpycore_types.cpp:156:24: error: ‘pyqt_td’ was not declared in this scope
pyqt4ClassTypeDef *pyqt_td = (pyqt4ClassTypeDef *)((sipWrapperType *)self)->type;
^
../../PyQt-x11-gpl-4.11.4/qpy/QtCore/qpycore_types.cpp:156:54: error: expected primary-expression before ‘)’ token
pyqt4ClassTypeDef *pyqt_td = (pyqt4ClassTypeDef *)((sipWrapperType *)self)->type;
^
../../PyQt-x11-gpl-4.11.4/qpy/QtCore/qpycore_types.cpp: In function ‘const QMetaObject* get_qmetaobject(pyqtWrapperType*)’:
../../PyQt-x11-gpl-4.11.4/qpy/QtCore/qpycore_types.cpp:820:52: error: ‘pyqt4ClassTypeDef’ was not declared in this scope
return reinterpret_cast<const QMetaObject *>(((pyqt4ClassTypeDef *)((sipWrapperType *)pyqt_wt)->type)->static_metaobject);
^
../../PyQt-x11-gpl-4.11.4/qpy/QtCore/qpycore_types.cpp:820:71: error: expected primary-expression before ‘)’ token
return reinterpret_cast<const QMetaObject *>(((pyqt4ClassTypeDef *)((sipWrapperType *)pyqt_wt)->type)->static_metaobject);
^
Makefile:1305: recipe for target 'qpycore_types.o' failed
make[1]: *** [qpycore_types.o] Error 1
make[1]: Leaving directory '/var/tmp/portage/dev-python/PyQt4-4.11.4-r1/work/PyQt-x11-gpl-4.11.4-python2_7/QtCore'
Makefile:49: recipe for target 'sub-QtCore-make_default-ordered' failed
make: *** [sub-QtCore-make_default-ordered] Error 2
* ERROR: dev-python/PyQt4-4.11.4-r1::gentoo failed (compile phase):
* emake failed
|
I slapped the full log et all to https://gist.github.com/STrRedWolf/3f7cd41a611aa10587648dfbcf1babd3 and wonder if the update to dev-python/sip-4.19 bombed everything. |
|
Back to top |
|
|
Hotblack n00b
Joined: 28 Dec 2004 Posts: 46
|
Posted: Sat Dec 31, 2016 10:25 pm Post subject: |
|
|
PyQt4-4.12 should compile fine with sip-4.19
In my case compilation failed with kde-apps/pykde4-4.14.3-r1, so I reverted to stable dev-python/sip-4.18 |
|
Back to top |
|
|
STrRedWolf n00b
Joined: 02 Sep 2002 Posts: 72
|
Posted: Mon Jan 02, 2017 3:37 am Post subject: |
|
|
And yet it doesn't. And I have PyQt5 compiled against sip-4.19, so it's forward or what. |
|
Back to top |
|
|
Hotblack n00b
Joined: 28 Dec 2004 Posts: 46
|
|
Back to top |
|
|
msst Apprentice
Joined: 07 Jun 2011 Posts: 259
|
Posted: Tue Jan 03, 2017 10:30 pm Post subject: |
|
|
Code: | qpycore_types.cpp:156:5: error: ‘pyqt4ClassTypeDef’ was not declared in this scope |
Exact same thing here. Is there currently a work-around? Downgrading python-sip perhaps? Not sure if that is blocked by another ~arch package... |
|
Back to top |
|
|
msst Apprentice
Joined: 07 Jun 2011 Posts: 259
|
Posted: Thu Jan 05, 2017 8:04 pm Post subject: |
|
|
Just to update - downgrading to the stable python-sip package fixes this and fortunately nothing is pulling in ~arch for this package. |
|
Back to top |
|
|
rburcham Apprentice
Joined: 20 Mar 2003 Posts: 243
|
Posted: Fri Feb 24, 2017 6:13 pm Post subject: |
|
|
I'm also trying to back out dev-python/sip-4.19.1 and roll back to 4.18, but I'm having trouble due to PyQT5 (and PyQT4)...
Code: | # emerge =dev-python/sip-4.19.1 --depclean -vp
Calculating dependencies * waiting for lock on /var/db/.pkg.portage_lockfile ... [ ok ]
... done!
dev-python/sip-4.19.1 pulled in by:
dev-python/PyQt4-4.12 requires >=dev-python/sip-4.19:=[python_targets_python2_7(-),python_targets_python3_4(-),-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-)], >=dev-python/sip-4.19:0/12=[python_targets_python2_7(-),python_targets_python3_4(-),-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-)]
dev-python/PyQt5-5.7.1 requires >=dev-python/sip-4.19:=[python_targets_python2_7(-),python_targets_python3_4(-),-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-)], >=dev-python/sip-4.19:0/12=[python_targets_python2_7(-),python_targets_python3_4(-),-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-)]
>>> No packages selected for removal by depclean
Packages installed: 2105
Packages in world: 379
Packages in system: 44
Required packages: 2105
Number to remove: 0 |
What do? It's explicitly asking for sip-4.19 in the PyQt* ebuilds' RDEPEND. |
|
Back to top |
|
|
asturm Developer
Joined: 05 Apr 2007 Posts: 8935
|
Posted: Fri Feb 24, 2017 6:23 pm Post subject: |
|
|
Why? Both your installed PyQt* versions are fine with sip-4.19. |
|
Back to top |
|
|
rburcham Apprentice
Joined: 20 Mar 2003 Posts: 243
|
Posted: Fri Feb 24, 2017 10:11 pm Post subject: |
|
|
Yes. But sip-4.19.1 is the problem, I'm trying to roll it back. Among other things one cannot build pykde4-4.14.3-r2 against it:
https://bugs.gentoo.org/show_bug.cgi?id=610650
And this is breaking a handful of apps with python guis, like crossover office.
I was able to work around this with:
Code: | # snip from /etc/portage/package.mask
=kde-apps/pykde4-4.14.3-r2
=dev-python/PyQt5-5.7.1
=dev-python/PyQt4-4.12
>dev-python/sip-4.18.1
|
|
|
Back to top |
|
|
asturm Developer
Joined: 05 Apr 2007 Posts: 8935
|
Posted: Fri Feb 24, 2017 10:19 pm Post subject: |
|
|
crossover-office-bin does not seem to have any business with python at all.
Moreover, you could try to get rid of pykde4 itself (by setting kdegames-meta[-python]). |
|
Back to top |
|
|
asturm Developer
Joined: 05 Apr 2007 Posts: 8935
|
Posted: Fri Feb 24, 2017 10:48 pm Post subject: |
|
|
...besides, pykde-4.14.3-r2 was supposedly fixed already to build with sip-4.19.1. When did you last sync your tree prior to building pykde? |
|
Back to top |
|
|
rburcham Apprentice
Joined: 20 Mar 2003 Posts: 243
|
Posted: Sat Feb 25, 2017 6:47 pm Post subject: |
|
|
The confirmed bug I referred to above is two days old and I synced and built a deep world on that day. When was pykde fixed? |
|
Back to top |
|
|
asturm Developer
Joined: 05 Apr 2007 Posts: 8935
|
Posted: Sat Feb 25, 2017 6:53 pm Post subject: |
|
|
Thanks, that's good to know. The fix for sip-4.19 actually went in on Mon Jan 9 2017 already, maybe 4.19.1 broke even more... |
|
Back to top |
|
|
STrRedWolf n00b
Joined: 02 Sep 2002 Posts: 72
|
Posted: Sat Feb 25, 2017 9:33 pm Post subject: |
|
|
FYI I worked around it by removing one package that depended on it and recompiling the HP printer drivers to not use the graphical interface.
Now to get my printer working again! (but that's another thread) |
|
Back to top |
|
|
Jara0 n00b
Joined: 08 Jan 2016 Posts: 22
|
Posted: Thu Mar 23, 2017 6:56 pm Post subject: |
|
|
It looks like sip-4.19 was removed from ebuilds and sip-4.19.1 is only item > than the required 4.19 for PyQt. It looks like it reintroduced that issue and PyQt4 fails to build.
Im having the same problem the user mentioned above when attempting to build PyQT4 against sip-4.19.1, im reluctant to switch the the 9999 version. Not sure if anyone else is having similar problems. Ill update if I find a fix/workaround. |
|
Back to top |
|
|
asturm Developer
Joined: 05 Apr 2007 Posts: 8935
|
Posted: Thu Mar 23, 2017 7:17 pm Post subject: |
|
|
dev-python/PyQt4-4.12 is the current stable, it builds fine against sip-4.19.1. |
|
Back to top |
|
|
|