[PyQt] PyKDE build failure with Sip 4.15.1
I've updated the Debian packages in the Debian Experimental repository for testing (just Sip 4.1.5 so far, but I'll upload 4.15.1 shortly). I tried rebuilding the current Debian PyKDE package (4.10.5) and it failed to build (last part of the build log attached). I tried locally with 4.15.1 and it still fails (the attached log is with 4.15.1.). I tried building the same package with sip 4.14.7 and it builds fine. Scott KScanning dependencies of target compile_python_files make[5]: Leaving directory `/home/pykde4-4.10.5/builddir-2.7' make -f CMakeFiles/compile_python_files.dir/build.make CMakeFiles/compile_python_files.dir/build make[5]: Entering directory `/home/pykde4-4.10.5/builddir-2.7' /usr/bin/cmake -E echo Byte-compiling\ /home/pykde4-4.10.5/builddir-2.7//__init__.py\ to\ /home/pykde4-4.10.5/builddir-2.7//__init__.pyc Byte-compiling /home/pykde4-4.10.5/builddir-2.7//__init__.py to /home/pykde4-4.10.5/builddir-2.7//__init__.pyc /usr/bin/cmake -E copy /home/pykde4-4.10.5/__init__.py /home/pykde4-4.10.5/builddir-2.7//__init__.py /usr/bin/python2.7 /usr/share/kde4/apps/cmake/modules/PythonCompile.py /home/pykde4-4.10.5/builddir-2.7//__init__.py /usr/bin/cmake -E echo Byte-compiling\ /home/pykde4-4.10.5/builddir-2.7//home/pykde4-4.10.5/builddir-2.7/pykdeconfig.py\ to\ /home/pykde4-4.10.5/builddir-2.7//home/pykde4-4.10.5/builddir-2.7/pykdeconfig.pyc Byte-compiling /home/pykde4-4.10.5/builddir-2.7//home/pykde4-4.10.5/builddir-2.7/pykdeconfig.py to /home/pykde4-4.10.5/builddir-2.7//home/pykde4-4.10.5/builddir-2.7/pykdeconfig.pyc /usr/bin/cmake -E copy /home/pykde4-4.10.5/builddir-2.7/pykdeconfig.py /home/pykde4-4.10.5/builddir-2.7//home/pykde4-4.10.5/builddir-2.7/pykdeconfig.py /usr/bin/python2.7 /usr/share/kde4/apps/cmake/modules/PythonCompile.py /home/pykde4-4.10.5/builddir-2.7//home/pykde4-4.10.5/builddir-2.7/pykdeconfig.py make[5]: Leaving directory `/home/pykde4-4.10.5/builddir-2.7' /usr/bin/cmake -E cmake_progress_report /home/pykde4-4.10.5/builddir-2.7/CMakeFiles [ 0%] Built target compile_python_files make -f CMakeFiles/python_module_PyKDE4_akonadi.dir/build.make CMakeFiles/python_module_PyKDE4_akonadi.dir/depend make[5]: Entering directory `/home/pykde4-4.10.5/builddir-2.7' /usr/bin/cmake -E cmake_progress_report /home/pykde4-4.10.5/builddir-2.7/CMakeFiles 2 [ 1%] Generating sip/akonadi/sipakonadipart0.cpp, sip/akonadi/sipakonadipart1.cpp, sip/akonadi/sipakonadipart2.cpp, sip/akonadi/sipakonadipart3.cpp, sip/akonadi/sipakonadipart4.cpp, sip/akonadi/sipakonadipart5.cpp, sip/akonadi/sipakonadipart6.cpp, sip/akonadi/sipakonadipart7.cpp /usr/bin/cmake -E echo touch /home/pykde4-4.10.5/builddir-2.7/sip/akonadi/sipakonadipart0.cpp /home/pykde4-4.10.5/builddir-2.7/sip/akonadi/sipakonadipart1.cpp /home/pykde4-4.10.5/builddir-2.7/sip/akonadi/sipakonadipart2.cpp /home/pykde4-4.10.5/builddir-2.7/sip/akonadi/sipakonadipart3.cpp /home/pykde4-4.10.5/builddir-2.7/sip/akonadi/sipakonadipart4.cpp /home/pykde4-4.10.5/builddir-2.7/sip/akonadi/sipakonadipart5.cpp /home/pykde4-4.10.5/builddir-2.7/sip/akonadi/sipakonadipart6.cpp /home/pykde4-4.10.5/builddir-2.7/sip/akonadi/sipakonadipart7.cpp /usr/bin/sip -t ALL -t WS_X11 -t Qt_4_8_4 -x VendorID -x PyQt_NoPrintRangeBug -g -x PyKDE_QVector -x Py_v3 -j 8 -c /home/pykde4-4.10.5/builddir-2.7/sip/akonadi -I /usr/share/sip/PyQt4 -I /home/pykde4-4.10.5/sip /home/pykde4-4.10.5/sip/akonadi/akonadimod.sip sip: Deprecation warning: /home/pykde4-4.10.5/sip/kdeui/kxmlguibuilder.sip:41: Annotations should not be used in explicit C/C++ signatures sip: Deprecation warning: /home/pykde4-4.10.5/sip/akonadi/itemserializerplugin.sip:33: Annotation is invalid cd /home/pykde4-4.10.5/builddir-2.7 /usr/bin/cmake -E cmake_depends Unix Makefiles /home/pykde4-4.10.5 /home/pykde4-4.10.5 /home/pykde4-4.10.5/builddir-2.7 /home/pykde4-4.10.5/builddir-2.7 /home/pykde4-4.10.5/builddir-2.7/CMakeFiles/python_module_PyKDE4_akonadi.dir/DependInfo.cmake --color= Scanning dependencies of target python_module_PyKDE4_akonadi make[5]: Leaving directory `/home/pykde4-4.10.5/builddir-2.7' make -f CMakeFiles/python_module_PyKDE4_akonadi.dir/build.make CMakeFiles/python_module_PyKDE4_akonadi.dir/build make[5]: Entering directory `/home/pykde4-4.10.5/builddir-2.7' /usr/bin/cmake -E cmake_progress_report /home/pykde4-4.10.5/builddir-2.7/CMakeFiles [ 1%] Building CXX object CMakeFiles/python_module_PyKDE4_akonadi.dir/sip/akonadi/sipakonadipart0.cpp.o /usr/bin/c++ -DKDE4_CMAKE_TOPLEVEL_DIR_LENGTH=5 -DKDE_DEPRECATED_WARNINGS -DQT3_SUPPORT -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NO_CAST_TO_ASCII -DQT_NO_STL -DUSING_SOPRANO_NRLMODEL_UNSTABLE_API -D_BSD_SOURCE -D_REENTRANT -D_XOPEN_SOURCE=500 -Dpython_module_PyKDE4_akonadi_EXPORTS -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -D_FORTIFY_SOURCE=2 -Wnon-virtual-dtor -Wno-long-long -Wundef -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -Wformat-security
Re: [PyQt] PyKDE build failure with Sip 4.15.1
On Saturday, August 24, 2013 06:07:25 Arfrever Frehtes Taifersar Arahesis wrote: 2013-08-24 05:17 Scott Kitterman napisał(a): I've updated the Debian packages in the Debian Experimental repository for testing (just Sip 4.1.5 so far, but I'll upload 4.15.1 shortly). I tried rebuilding the current Debian PyKDE package (4.10.5) and it failed to build (last part of the build log attached). I tried locally with 4.15.1 and it still fails (the attached log is with 4.15.1.). https://bugs.kde.org/show_bug.cgi?id=323899 There weren't supposed to be any incompatible changes in 4.15, just extensions (which is why SIP API went from 10 to 10.1, not 11). I don't think it's a PyKDE bug. Scott K ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] PyQt5 module not found
Shriramana Sharma samj...@gmail.com wrote: Hello. Trying to compile PyQt5 on my Kubuntu Raring system, I had problems: the SIP version was too old, backporting the latest from Debian broke the existing PyQt4 packages because they depend on an older SIP API, and that removed the existing PyQt4/PyKDE4/PyQsci-based apps, so I rebuilt the latest version of all those against the latest SIP, and then installed everything and finally compiled PyQt5. This is all fixed now. It's also off topic here I think since it's just packaging. Scott K ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Problem with Sip for Py3 on Debian/Ubuntu
Phil Thompson p...@riverbankcomputing.com wrote: On Tue, 25 Jun 2013 20:46:57 +0530, Shriramana Sharma samj...@gmail.com wrote: On Tue, Jun 25, 2013 at 8:19 PM, Phil Thompson p...@riverbankcomputing.com wrote: The code generator is the same for all Python versions. Hi thanks for this quick [as always! :-)] reply! So then it seems to me that the packaging should be changed. Currently the sip4 source package (http://packages.debian.org/source/sid/sip4) produces these binary packages: python-sip: runtime library python-sip-dbg: runtime library (debug extension) python-sip-dev: development files python-sip-doc: documentation python3-sip: runtime library python3-sip-dbg: runtime library (debug extension) python3-sip-dev: development files It would seem that the common code generator should be moved to python-sip-dev-common and python-sip-dev and python3-sip-dev should both depend on it. python-sip-doc should also be moved to python-sip-doc-common. Does that sound about right? If OK, I can file a Debian bug for this. I don't care - nothing to do with me. I'll take a look at it. Scott K ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] ANN: SIP v4.14.7 Released
On Monday, June 17, 2013 10:13:32 AM Phil Thompson wrote: SIP v4.14.7 has been released. This is a minor functional release but is required by PyQt v5. It would be nice if new SIP versions that introduce a new major API version number weren't described as a minor functional release. It seems to me that incompatible API changes are rather more than that. Scott K ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] ANN: SIP v4.14.7 Released
On Tuesday, June 18, 2013 11:21:33 PM Phil Thompson wrote: On Tue, 18 Jun 2013 16:40:25 -0400, Scott Kitterman deb...@kitterman.com wrote: On Monday, June 17, 2013 10:13:32 AM Phil Thompson wrote: SIP v4.14.7 has been released. This is a minor functional release but is required by PyQt v5. It would be nice if new SIP versions that introduce a new major API version number weren't described as a minor functional release. It seems to me that incompatible API changes are rather more than that. They are not incompatible API changes, they are incompatible ABI changes - an implementation detail. Since we (Debian/Ubuntu) distribute binaries that make use of the ABI, it's a non-trivial one for us. We have to rebuild the relevant packages each time this happens. Scott K ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
[PyQt] segfault when calling PyQt4.QtGui.QIcon.themeSearchPaths()
I'm not if this is an actual bug or a user error, but a PyQt bug was just filed in Debian: bugs.debian.org/cgi-bin/bugreport.cgi?bug=702445 The reporter has 4.9.3, but I get the same with 4.9.6 and 4.10: Python 2.7.3 (default, Jan 26 2013, 15:27:56) [GCC 4.7.2] on linux2 Type help, copyright, credits or license for more information. import PyQt4.QtGui PyQt4.QtGui.QIcon.themeSearchPaths() Segmentation fault (core dumped) Scott K ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] segfault when calling PyQt4.QtGui.QIcon.themeSearchPaths()
On Wednesday, March 06, 2013 10:14:22 PM Phil Thompson wrote: On Wed, 06 Mar 2013 14:51:35 -0500, Scott Kitterman deb...@kitterman.com wrote: I'm not if this is an actual bug or a user error, but a PyQt bug was just filed in Debian: bugs.debian.org/cgi-bin/bugreport.cgi?bug=702445 The reporter has 4.9.3, but I get the same with 4.9.6 and 4.10: Python 2.7.3 (default, Jan 26 2013, 15:27:56) [GCC 4.7.2] on linux2 Type help, copyright, credits or license for more information. import PyQt4.QtGui PyQt4.QtGui.QIcon.themeSearchPaths() Segmentation fault (core dumped) Almost certainly a user error/Qt feature. Try creating a QApplication instance first. Thank you. I've passed that on to the bug reporter. Scott K ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
[PyQt] Specifying Qscintilla2 Include Directories When Building with PyQt 4.10
You may recall that last year I had an issue with the fact that due to the
Debian/Ubuntu multi-arch implementation, I need to include headers from two
different directories (one common and one arch specific):
http://www.riverbankcomputing.com/pipermail/pyqt/2012-October/032049.html
With the new Qscintilla2 Python/configure.py I ran into the same problem and
solved it similarly. Patch is attached. Is this an appropriate approach? It
appears to work for both Python and Python3.
Scott KAdded to support multiple Python header directories for multi-arch
-I/usr/include/i386-linux-gnu/python2.7
Patch by Scott Kitterman sc...@kitterman.com, will be sent upstream
Index: qscintilla2-2.7.1/Python/configure.py
===
--- qscintilla2-2.7.1.orig/Python/configure.py 2013-03-06 16:46:05.860789440 -0500
+++ qscintilla2-2.7.1/Python/configure.py 2013-03-06 23:49:14.13060 -0500
@@ -96,6 +96,7 @@
if hasattr(sysconfig, 'get_path'):
# The modern API.
self.inc_dir = sysconfig.get_path('include')
+self.py_conf_inc_dir = os.path.dirname(sysconfig.get_config_h_filename())
self.module_dir = sysconfig.get_path('platlib')
else:
# The legacy distutils API.
@@ -154,6 +155,7 @@
self.pyqt_sip_dir = os.path.join(py_config.data_dir, 'sip', 'PyQt4')
self.qsci_sip_dir = self.pyqt_sip_dir
self.py_inc_dir = py_config.inc_dir
+self.py_conf_inc_dir = py_config.py_conf_inc_dir
self.sip_inc_dir = py_config.inc_dir
self.py_lib_dir = py_config.lib_dir
@@ -649,6 +651,8 @@
pro.write('INCLUDEPATH += %s\n' % target_config.qsci_inc_dir)
pro.write('INCLUDEPATH += %s\n' % target_config.py_inc_dir)
+if target_config.py_inc_dir != target_config.py_conf_inc_dir:
+pro.write('INCLUDEPATH += %s\n' % target_config.py_conf_inc_dir)
if target_config.py_inc_dir != target_config.sip_inc_dir:
pro.write('INCLUDEPATH += %s\n' % target_config.sip_inc_dir)
___
PyQt mailing listPyQt@riverbankcomputing.com
http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] PyQt for University Project
You absolutely can as long as you comply with the license. Scott K Joe Borġ m...@jdborg.com wrote: Are you going to sell the product, or use use it as your University project? If it's the latter, you're fine. But I don't think you can use PyQt (or Qt libraries) for profit. Regards, Joseph David Borġ http://www.jdborg.com On 21 January 2013 17:19, Moore John moorejoh...@googlemail.com wrote: Hi, I am a final year student of University of Greenwich. I am studying at a course of BIT(Hons). I am doing a project that a software base on Python language and will be running on Linux platform. I want to know, am I possible to use PyQt4 in my software program without given a license fee for using that. I will be waiting your reply because my time frame is limit and if not possible I have to choose another GUI toolkits. Regards, Moore John ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] problem running pyqt on xubuntu
On Saturday, October 20, 2012 08:11:29 AM Mark Summerfield wrote: I have built local versions of Qt 4.8.3, Python, SIP, and PyQt on an Xubuntu machine which has Qt 4.8.1 as its system Qt: ... So clearly, despite trying to build using my local Qt, PyQt seems to be looking at the system Qt. Is there a solution for this? Upgrading to the newest Xubuntu release where 4.8.3 is the system Qt would be one way to do it. Scott K ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
[PyQt] Specifying Include Directories for PyQt Build
Starting with python3.3, python will support multiarch [1] in Debian and Ubuntu. As part of this change, the path for some of the Python header files has changed, so I need to specify multiple include directories. Here's an example using pkg-config so show the difference between python3.2 and python3.3 on an i386 system: $ pkg-config --cflags-only-I python-3.2mu -I/usr/include/python3.2mu $ pkg-config --cflags-only-I python-3.3m -I/usr/include/python3.3m -I/usr/include/i386-linux-gnu/python3.3m So how do I specify both directories for building with this multi-arch'ed python3.3? Any advice appreciated. Scott K [1] http://wiki.debian.org/Multiarch ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Specifying Include Directories for PyQt Build
On Saturday, October 20, 2012 08:44:25 PM Scott Kitterman wrote: Starting with python3.3, python will support multiarch [1] in Debian and Ubuntu. As part of this change, the path for some of the Python header files has changed, so I need to specify multiple include directories. Here's an example using pkg-config so show the difference between python3.2 and python3.3 on an i386 system: $ pkg-config --cflags-only-I python-3.2mu -I/usr/include/python3.2mu $ pkg-config --cflags-only-I python-3.3m -I/usr/include/python3.3m -I/usr/include/i386-linux-gnu/python3.3m So how do I specify both directories for building with this multi-arch'ed python3.3? Any advice appreciated. Scott K [1] http://wiki.debian.org/Multiarch Nevermind. I think I understand the problem now. Scott K ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Specifying Include Directories for PyQt Build
On Saturday, October 20, 2012 10:42:07 PM Scott Kitterman wrote: On Saturday, October 20, 2012 08:44:25 PM Scott Kitterman wrote: Starting with python3.3, python will support multiarch [1] in Debian and Ubuntu. As part of this change, the path for some of the Python header files has changed, so I need to specify multiple include directories. Here's an example using pkg-config so show the difference between python3.2 and python3.3 on an i386 system: $ pkg-config --cflags-only-I python-3.2mu -I/usr/include/python3.2mu $ pkg-config --cflags-only-I python-3.3m -I/usr/include/python3.3m -I/usr/include/i386-linux-gnu/python3.3m So how do I specify both directories for building with this multi-arch'ed python3.3? Any advice appreciated. Scott K [1] http://wiki.debian.org/Multiarch Nevermind. I think I understand the problem now. I had it half solved. Once I fixed my sip4 build, the arch specific directory was captured by sip in py_conf_inc_dir and I had correct includes for the directories configured by sip, but not for qpy. Adding the patch below to configure.py solved that by adding it to the qpy .pro files. Is this a reasonable way to handle it and would you consider this an appropriate change for upstream? Scott K Index: python-qt4-4.9.3/configure.py === --- python-qt4-4.9.3.orig/configure.py 2012-10-21 04:38:26.0 + +++ python-qt4-4.9.3/configure.py 2012-10-21 04:40:50.912484733 + @@ -811,6 +811,9 @@ if sipcfg.sip_inc_dir != sipcfg.py_inc_dir: inc_path.insert(0, sipcfg.sip_inc_dir) +if sipcfg.py_inc_dir != sipcfg.py_conf_inc_dir: + inc_path.insert(0, sipcfg.py_conf_inc_dir) + if opts.bigqt: api_dir = ../../_qt else ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] latest pykde4 (4.9.2) build fails against new sip-4.14/PyQt-4.9.5
On Wednesday, October 03, 2012 10:23:16 AM Luca Beltrame wrote: In data martedì 2 ottobre 2012 12:35:10, Scott Kitterman ha scritto: Is there a chance you could IFDEF that instead of just removing the definition so that 4.10 can be backported to releases with the older PyQt? I'm not sure of the current views from Simon Edwards (PyKDE4's maintaienr), but AFAIK, master branch has always required the latest SIP + PyQT. It would make it possible to run PyKDE4 4.10 on both Debian Wheezy and Ubuntu Quantal (12.10) without having to revert the changes for the newer SIP/PyQT (since it's too late in the release cycle to update them before release). Scott K ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] latest pykde4 (4.9.2) build fails against new sip-4.14/PyQt-4.9.5
On Wednesday, October 03, 2012 03:21:02 PM Luca Beltrame wrote: In data mercoledì 3 ottobre 2012 14:16:33, Phil Thompson ha scritto: In your configure.py (or whatever) pass -x PyKDE_UseMyMappedType to sip in order to *disable* it. Thanks, I have an idea of how to do this then. Scott, do you have time constraints? I'll have to touch the build system (for the sip options), so I don't think I'll be able to work on this properly till the weekend. Not immediate ones. As long as it gets into 4.10 by it's beta release, it won't affect anything we have to do. Scott K ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] latest pykde4 (4.9.2) build fails against new sip-4.14/PyQt-4.9.5
On Wednesday, October 03, 2012 09:43:24 PM Luca Beltrame wrote: In data mercoledì 03 ottobre 2012 09:31:57, Scott Kitterman ha scritto: Not immediate ones. As long as it gets into 4.10 by it's beta release, it won't affect anything we have to do. Turns out it was quite easy to do: try fd30259903ad693b86476b6e8c280b93d0102223 from the 4.9 branch and see if it builds (it should). For reference, which PyQt version will you be targeting there? I need to know to adjust the if statements correctly. First I tried to build with your patch applied to PyKDE 4.8 (current Debian version) and got this error: sip: /home/pykde4-4.8.4/sip/akonadi/item.sip:74: Akonadi::Item::availablePayloadMetaTypeIds() unsupported function return type - provide %MethodCode and a C++ signature make[5]: *** [sip/akonadi/sipakonadipart0.cpp] Error 1 That's using Sip 4.13.3 and PyQt 4.9.3 (which are the versions I'll be targeting for both Debian and Ubuntu). It gets past that point with Sip 4.14 and PyQt 4.9.5. Thanks for working on this. Scott K ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] latest pykde4 (4.9.2) build fails against new sip-4.14/PyQt-4.9.5
On Wednesday, October 03, 2012 11:28:48 PM Luca Beltrame wrote: In data mercoledì 03 ottobre 2012 23:22:46, Luca Beltrame ha scritto: Can you give me the hex version of PyQt? I'll adjust the check and see whether it works or not. I made the check a little less lax. Can you try and see whether it works now? Yes. That works. I tried building PyKDE4 4.8.4 with the version of the patch and it appears it will build both with PyQt 4.9.3 and 4.9.5. Just what I was looking for. Thanks, Scott K ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] latest pykde4 (4.9.2) build fails against new sip-4.14/PyQt-4.9.5
On Monday, October 01, 2012 11:46:52 AM Rex Dieter wrote: Get a bunch of these trying to (re)build pykde4 against recent sip/PyQt release: sip: /builddir/build/BUILD/pykde4-4.9.2/sip/kdecore/typedefs.sip:955: Mapped type has already been defined in another module make[2]: *** [sip/dnssd/sipdnssdpart0.cpp] Error 1 make[2]: Leaving directory `/builddir/build/BUILD/pykde4-4.9.2/x86_64- redhat-linux-gnu' make[1]: *** [CMakeFiles/python_module_PyKDE4_dnssd.dir/all] Error 2 make[1]: *** Waiting for unfinished jobs sip: /builddir/build/BUILD/pykde4-4.9.2/sip/kdecore/typedefs.sip:955: Mapped type has already been defined in another module make[2]: *** [sip/kdecore/sipkdecorepart0.cpp] Error 1 make[2]: Leaving directory `/builddir/build/BUILD/pykde4-4.9.2/x86_64- redhat-linux-gnu' make[1]: *** [CMakeFiles/python_module_PyKDE4_kdecore.dir/all] Error 2 sip: /builddir/build/BUILD/pykde4-4.9.2/sip/kdecore/typedefs.sip:955: Mapped type has already been defined in another module make[2]: *** [sip/akonadi/sipakonadipart0.cpp] Error 1 make[2]: Leaving directory `/builddir/build/BUILD/pykde4-4.9.2/x86_64- redhat-linux-gnu' make[1]: *** [CMakeFiles/python_module_PyKDE4_akonadi.dir/all] Error 2 sip: /builddir/build/BUILD/pykde4-4.9.2/sip/kdecore/typedefs.sip:955: Mapped type has already been defined in another module make[2]: *** [sip/kdeui/sipkdeuipart0.cpp] Error 1 Same error in Debian with 4.8.2. Scott K ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] latest pykde4 (4.9.2) build fails against new sip-4.14/PyQt-4.9.5
On Tuesday, October 02, 2012 04:32:34 PM Luca Beltrame wrote: In data martedì 2 ottobre 2012 10:27:33, Scott Kitterman ha scritto: Same error in Debian with 4.8.2. I fixed it in PyKDE4's git repository by removing the duplicated definition. However I can't backport it because it would break for previous versions of SIP and PyQt (and I can't bump versions on minor releases). Apply 017822bd0dfc83fe9a7a483ecc33f4aab839a3c6 from git master to your packages and it should build. Thanks. It does. Is there a chance you could IFDEF that instead of just removing the definition so that 4.10 can be backported to releases with the older PyQt? Scott K ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] PyQt4 Support for Qt v5-beta1
Phil Thompson p...@riverbankcomputing.com wrote: The current PyQt snapshot has support for the following modules built against Qt v5-beta1... QtCore, QtGui, QtHelp, QtNetwork, QtSql, QtSvg, QtWebKit, QtXml You will also need current SIP and QScintilla snapshots. Are you planning a new set of releases soon? Scott K ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] pyuic issue with 4.9.3
Phil Thompson p...@riverbankcomputing.com wrote: On Fri, 13 Jul 2012 09:02:30 -0400, Scott Kitterman deb...@kitterman.com wrote: On Friday, July 13, 2012 01:40:38 PM Phil Thompson wrote: On Wed, 11 Jul 2012 20:07:46 -0400, Scott Kitterman deb...@kitterman.com wrote: If you run pyuic4 -o video_ui.py video.ui with the two attached files, it works fine with 4.9.1, but fails with 4.9.3. The error I get is: Unknown Qt widget: Phonon.VideoPlayer Was there a change that weboob (where the two files were taken from) needs to adapt to? No, it's a bug - fixed in tonight's snapshot. Great. If you could give me the patch for this issue against 4.9.3, that'd be a great help (I'm not going to get a newer version into Debian at this point, so I need to deal in patches). I can diff the snapshots, but it'd be nice to just have the patch. Attached. Thank you, Scott K ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] pyuic issue with 4.9.3
On Friday, July 13, 2012 01:40:38 PM Phil Thompson wrote: On Wed, 11 Jul 2012 20:07:46 -0400, Scott Kitterman deb...@kitterman.com wrote: If you run pyuic4 -o video_ui.py video.ui with the two attached files, it works fine with 4.9.1, but fails with 4.9.3. The error I get is: Unknown Qt widget: Phonon.VideoPlayer Was there a change that weboob (where the two files were taken from) needs to adapt to? No, it's a bug - fixed in tonight's snapshot. Great. If you could give me the patch for this issue against 4.9.3, that'd be a great help (I'm not going to get a newer version into Debian at this point, so I need to deal in patches). I can diff the snapshots, but it'd be nice to just have the patch. Thanks, Scott K ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
[PyQt] pyuic issue with 4.9.3
If you run pyuic4 -o video_ui.py video.ui with the two attached files, it works fine with 4.9.1, but fails with 4.9.3. The error I get is: Unknown Qt widget: Phonon.VideoPlayer Was there a change that weboob (where the two files were taken from) needs to adapt to? Scott K# -*- coding: utf-8 -*- # Form implementation generated from reading ui file 'video.ui' # # Created: Thu Jul 12 00:03:34 2012 # by: PyQt4 UI code generator 4.9.3 # # WARNING! All changes made in this file will be lost! from PyQt4 import QtCore, QtGui try: _fromUtf8 = QtCore.QString.fromUtf8 except AttributeError: _fromUtf8 = lambda s: s class Ui_Video(object): def setupUi(self, Video): Video.setObjectName(_fromUtf8(Video)) Video.resize(647, 404) self.verticalLayout = QtGui.QVBoxLayout(Video) self.verticalLayout.setObjectName(_fromUtf8(verticalLayout)) self.titleLabel = QtGui.QLabel(Video) font = QtGui.QFont() font.setPointSize(12) font.setBold(True) font.setWeight(75) self.titleLabel.setFont(font) self.titleLabel.setFrameShape(QtGui.QFrame.Box) self.titleLabel.setFrameShadow(QtGui.QFrame.Raised) self.titleLabel.setAlignment(QtCore.Qt.AlignCenter) self.titleLabel.setObjectName(_fromUtf8(titleLabel)) self.verticalLayout.addWidget(self.titleLabel) self.frame = QtGui.QFrame(Video) sizePolicy = QtGui.QSizePolicy(QtGui.QSizePolicy.Preferred, QtGui.QSizePolicy.MinimumExpanding) sizePolicy.setHorizontalStretch(0) sizePolicy.setVerticalStretch(0) sizePolicy.setHeightForWidth(self.frame.sizePolicy().hasHeightForWidth()) self.frame.setSizePolicy(sizePolicy) self.frame.setStyleSheet(_fromUtf8(background-color: rgb(255, 255, 255);)) self.frame.setFrameShape(QtGui.QFrame.StyledPanel) self.frame.setFrameShadow(QtGui.QFrame.Sunken) self.frame.setObjectName(_fromUtf8(frame)) self.verticalLayout_2 = QtGui.QVBoxLayout(self.frame) self.verticalLayout_2.setObjectName(_fromUtf8(verticalLayout_2)) video.ui Description: application/designer signature.asc Description: This is a digitally signed message part. ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Compiler Flags and PyQt
On Monday, June 25, 2012 08:55:30 PM Hans-Peter Jansen wrote: @Scott: here's how I solved this (line 96 ff.): https://build.opensuse.org/package/view_file?file=python-qt4.specpackage=py thon-qt4project=home%3Afrispete%3APyQtrev=6161032f9d1629c3293dd3356c02dc49 Thank you. I'll give something like that a shot (until maybe I get the Debian Qt maintainers to change it there). Scott K ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Compiler Flags and PyQt
On Sunday, June 24, 2012 06:32:44 PM Phil Thompson wrote: ... If these flags are Debian standard then why not add them to Qt's spec file for Debian? PyQt will then pick them up automatically. Thanks for the suggestion. I'm not the Debian Qt maintainer, so I can't just do it, but I'll discuss it with them. Scott K ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Is the download of sip and pyqt4 the same for 2.7 and 3.2?
I tried this out in an 11.04 chroot. Things that get overwritten from the distributionPyQt package: /usr/share/sip/PyQt4/ /usr/bin/pyuic4 /usr/bin/pylupdate4 /usr/bin/pyrcc4 /usr/lib/qt4/plugins/designer/libpythonplugin.so (designer plugin) Except for the designer plugin, these are all shipped in separate packages called pyqt4-dev-tools and python-qt4-dev that are only used for development support. On that basis, I think it's very unlikely that building the python3 version from source would break your system, but keep in mind that this is unsupported (from my POV anyway) and if you do break it somehow, you get to keep both halves. Scott K On Sunday, June 24, 2012 02:59:44 PM Vayu wrote: If I leave the 2.7 stuff as is, what will happen to the stuff the manual install puts in /usr/bin will it overwrite the PyQt and sip from the previous package install for Python 2.7 and possibly break it or will it be putting differently named stuff there? On Sunday, June 24, 2012 02:17:18 PM Phil Thompson wrote: On Sun, 24 Jun 2012 11:56:45 -0700, Vayu v...@sklinks.com wrote: Is the download of sip and pyqt4 the same for 2.7 and 3.2? Yes. The following is more of an install issue, I hope it's not inappropriate to ask here. I downloaded the latest version of sip/pyqt4 and the message from .configure indicated it was going to put some stuff in /usr/bin (and some in a python3.2 directory). I already have 2.7 installed from my package manager (Ubuntu 11.04) and am thinking that my existing install for 2.7 must have stuff in /usr/bin and might break. Should I unistall everything sip and pyqt4 related and then run configure.py/make/make install separately for both 2.7 and then 3.2? On the plus side that will give you the same version of PyQt for both versions of Python. On the minus side there may be other applications that depend on the version of PyQt that Ubuntu installs for Python2. Or can I go ahead and leave 2.7 as is and just manually install for 3.2? (my package manager had python 3.2 but not sip and pyqt4 for it.) On the plus side you are not changing Ubuntu's defaults. On the minus side the version of PyQt you use with Python3 may be different to the version you use with Python2. Phil ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Extending configure.py/siputils.py to pass CPPFLAGS
On Saturday, June 23, 2012 10:15:13 AM Phil Thompson wrote:
On Sat, 23 Jun 2012 10:07:02 +0100, Andrew Suffield
asuffi...@suffields.me.uk wrote:
On Sat, Jun 23, 2012 at 09:57:56AM +0100, Phil Thompson wrote:
Why? Does Debian need it to be called CPPFLAGS specifically rather than
the already supported CXXFLAGS?
I'm going to guess that you've made the common mistake. CPPFLAGS is
the preprocessor flags, not the C++ compiler flags. Hence invocations
would be:
gcc $(CFLAGS) $(CPPFLAGS)
g++ $(CXXFLAGS) $(CPPFLAGS)
cpp $(CPPFLAGS)
Good guess :)
However the point remains that it can be achieved with existing
functionality.
It can. I thought it would be more correct to extend configure, but if you'd
rather not I can just CXXFLAGS=${CXXFLAGS} ${CPPFLAGS}. That's why I sent
you the patch for review before applying it to Debian.
Scott K
___
PyQt mailing listPyQt@riverbankcomputing.com
http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] PyQt 4.9.2 build failure with Python3.2
On Friday, June 22, 2012 09:03:33 AM Phil Thompson wrote: On Thu, 21 Jun 2012 22:26:37 -0400, Scott Kitterman deb...@kitterman.com wrote: PyQt 4.9.1 builds fine with all the Pythons we currently have in Debian Unstable (2.6/2.7/3.2). PyQt 4.9.2 does fine building with 2.6/2.7, but fails with Python3.2. I've attached the excerpt of the build log relevant to the 3.2 build. I'd appreciate advice on how to troubleshoot this. Scott K It would suggest you haven't installed sip for that version of Python. Phil I do have it. /usr/include/python3.2/sip.h exists in the build environment (and it is 4.13.3). Any other suggestions? Scott K ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] PyQt 4.9.2 build failure with Python3.2
On Friday, June 22, 2012 04:14:08 PM Phil Thompson wrote: On Fri, 22 Jun 2012 10:52:22 -0400, Scott Kitterman deb...@kitterman.com wrote: On Friday, June 22, 2012 09:03:33 AM Phil Thompson wrote: On Thu, 21 Jun 2012 22:26:37 -0400, Scott Kitterman deb...@kitterman.com wrote: PyQt 4.9.1 builds fine with all the Pythons we currently have in Debian Unstable (2.6/2.7/3.2). PyQt 4.9.2 does fine building with 2.6/2.7, but fails with Python3.2. I've attached the excerpt of the build log relevan to the 3.2 build. I'd appreciate advice on how to troubleshoot this. Scott K It would suggest you haven't installed sip for that version of Python. Phil I do have it. /usr/include/python3.2/sip.h exists in the build environment (and it is 4.13.3). Any other suggestions? From your build log it looks like it should be in /usr/include/python3.2mu Phil Yes. That was exactly the problem. Thank you for your help. Scott K ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
[PyQt] Extending configure.py/siputils.py to pass CPPFLAGS
In order to support Debian's goal to have a common set of default build flags for the distribution (with a particular focus on hardening related changes), I need to pass CPPFLAGS through configure. I came up with the attached patch for sip4 0.13.3. I'd appreciate a review. It works. I won't say much for it beyond that as I'm not sure I've fully grokked what's going on in siputils.py. If this seams reasonable, I intend to attack PyQt4 and QScintilla2 also. Scott K Description: Extend configure.py and siputils.py to support external definition of CPPFLAGS Author: Scott Kitterman sc...@kitterman.com Origin: vendor Forwarded: no Reviewed-By: Scott Kitterman sc...@kitterman.com Last-Update: 2012-06-22 --- sip4-4.13.3.orig/configure.py +++ sip4-4.13.3/configure.py @@ -63,6 +63,7 @@ build_macro_names = [ CFLAGS_STL_ON, CFLAGS_STL_OFF, CFLAGS_WARN_ON, CFLAGS_WARN_OFF, CHK_DIR_EXISTS, COPY, +CPPFLAGS, CPPFLAGS_SHLIB, CPPFLAGS_RELEASE, CXX, CXXFLAGS, CXXFLAGS_RELEASE, CXXFLAGS_DEBUG, --- sip4-4.13.3.orig/siputils.py +++ sip4-4.13.3/siputils.py @@ -313,6 +313,7 @@ class Makefile: # These are what configuration scripts normally only need to change. self.extra_cflags = [] +self.extra_cppflags = [] self.extra_cxxflags = [] self.extra_defines = [] self.extra_include_dirs = [] @@ -369,6 +370,10 @@ class Makefile: cflags.extend(self.extra_cflags) cflags.extend(self.optional_list(CFLAGS)) +cppflags = _UniqueList() +cppflags.extend(self.extra_cppflags) +cppflags.extend(self.optional_list(CPPFLAGS)) + cxxflags = _UniqueList() cxxflags.extend(self.extra_cxxflags) cxxflags.extend(self.optional_list(CXXFLAGS)) @@ -767,6 +772,7 @@ class Makefile: # Save the transformed values. self.CFLAGS.set(cflags) +self.CPPFLAGS.set(cppflags) self.CXXFLAGS.set(cxxflags) self.DEFINES.set(defines) self.INCDIR.set(incdir) @@ -1098,7 +1104,7 @@ class Makefile: mfile.write(CXX = %s\n % self.required_string(CXX)) mfile.write(LINK = %s\n % self.required_string(LINK)) -cppflags = [] +cppflags = [self.optional_string(CPPFLAGS),] if not self._debug: cppflags.append(-DNDEBUG) @@ -1461,6 +1467,7 @@ class ModuleMakefile(Makefile): self.DEFINES.append(SIP_STATIC_MODULE) else: self.CFLAGS.extend(self.optional_list(CFLAGS_SHLIB)) +self.CPPFLAGS.extend(self.optional_list(CPPFLAGS_SHLIB)) self.CXXFLAGS.extend(self.optional_list(CXXFLAGS_SHLIB)) lflags_dll = self.optional_list(LFLAGS_DLL) @@ -1807,6 +1814,7 @@ class ProgramMakefile(Makefile): build.append(-I + _quote(f)) build.extend(self.optional_list(CXXFLAGS)) +build.extend(self.optional_list(CPPFLAGS)) # Borland requires all flags to precede all file names. if self.generator != BMAKE: ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
[PyQt] Another configure/linking related patch
This one should have been forwarded as well. Scott K Index: python-qt4-4.9.2/configure.py === --- python-qt4-4.9.2.orig/configure.py 2012-06-21 15:56:58.711290073 -0400 +++ python-qt4-4.9.2/configure.py 2012-06-21 15:58:14.647287829 -0400 @@ -348,10 +348,10 @@ if opts.mwg_ssl_dir: ass_lib_dirs = [os.path.join(opts.mwg_ssl_dir, lib)] -ass_libs = [ssleay32, libeay32] +ass_libs = [ssleay32, libeay32, QtCore] else: ass_lib_dirs = None -ass_libs = None +ass_libs = [QtCore] # Note that the order in which we check is important for the # consolidated module - a module's dependencies must be checked first. ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
[PyQt] PyQt 4.9.2 build failure with Python3.2
PyQt 4.9.1 builds fine with all the Pythons we currently have in Debian Unstable (2.6/2.7/3.2). PyQt 4.9.2 does fine building with 2.6/2.7, but fails with Python3.2. I've attached the excerpt of the build log relevant to the 3.2 build. I'd appreciate advice on how to troubleshoot this. Scott K mkdir -p build-3.2 cd build-3.2 python3.2 ../configure.py --confirm-license --verbose -q /usr/bin/qmake-qt4 -c -j 10 LIBDIR_QT=/usr/lib STRIP= MOC=moc-qt4 LIBS_OPENGL= LIBS_X11= LIBS_THREAD= LFLAGS= CXXFLAGS_RELEASE=-Os LFLAGS_RELEASE=-Wl,-O1 \ -m /usr/lib/python3.2/config \ -d /usr/lib/python3.2/dist-packages \ --dbus /usr/include/dbus-1.0 \ --no-designer-plugin Determining the layout of your Qt installation... /usr/bin/qmake-qt4 -o qtdirs.mk qtdirs.pro make -f qtdirs.mk make[1]: Entering directory `/home/python-qt4-4.9.2/build-3.2' g++ -c -pipe -O2 -Wall -W -D_REENTRANT -DQT_WEBKIT -DQT_NO_DEBUG -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++ -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4 -I. -o qtdirs.o qtdirs.cpp g++ -Wl,-O1 -o qtdirs qtdirs.o-L/usr/lib/i386-linux-gnu -lQtCore -lpthread make[1]: Leaving directory `/home/python-qt4-4.9.2/build-3.2' ./qtdirs This is the GPL version of PyQt 4.9.2 (licensed under the GNU General Public License) for Python 3.2.3 on linux2. Found the license file pyqt-gpl.sip. Checking to see if the QtGui module should be built... g++ -DQT_NO_DEBUG -DQT_GUI_LIB -I. -I/usr/mkspecs/linux-g++ -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I/usr/X11R6/include -pipe -Os -w -D_REENTRANT cfgtest_QtGui.cpp -o cfgtest_QtGui -L/usr/lib -L/usr/X11R6/lib -Wl,-O1 -lQtGui Checking to see if the QtHelp module should be built... g++ -DQT_NO_DEBUG -I. -I/usr/mkspecs/linux-g++ -I/usr/include/qt4/QtHelp -I/usr/include/qt4 -pipe -Os -w -D_REENTRANT cfgtest_QtHelp.cpp -o cfgtest_QtHelp -L/usr/lib -Wl,-O1 -lQtCore -lQtHelp Checking to see if the QtMultimedia module should be built... g++ -DQT_NO_DEBUG -DQT_MULTIMEDIA_LIB -I. -I/usr/mkspecs/linux-g++ -I/usr/include/qt4/QtMultimedia -I/usr/include/qt4 -pipe -Os -w -D_REENTRANT cfgtest_QtMultimedia.cpp -o cfgtest_QtMultimedia -L/usr/lib -Wl,-O1 -lQtMultimedia cfgtest_QtMultimedia.cpp:1:28: fatal error: QAudioDeviceInfo: No such file or directory compilation terminated. Checking to see if the QtNetwork module should be built... g++ -DQT_NO_DEBUG -DQT_NETWORK_LIB -I. -I/usr/mkspecs/linux-g++ -I/usr/include/qt4/QtNetwork -I/usr/include/qt4 -pipe -Os -w -D_REENTRANT cfgtest_QtNetwork.cpp -o cfgtest_QtNetwork -L/usr/lib -Wl,-O1 -lQtNetwork Checking to see if the QtDBus module should be built... g++ -DQT_NO_DEBUG -I. -I/usr/mkspecs/linux-g++ -I/usr/include/qt4/QtDBus -I/usr/include/qt4 -pipe -Os -w -D_REENTRANT cfgtest_QtDBus.cpp -o cfgtest_QtDBus -L/usr/lib -Wl,-O1 -lQtDBus Checking to see if the QtDeclarative module should be built... g++ -DQT_NO_DEBUG -DQT_DECLARATIVE_LIB -I. -I/usr/mkspecs/linux-g++ -I/usr/include/qt4/QtDeclarative -I/usr/include/qt4 -pipe -Os -w -D_REENTRANT cfgtest_QtDeclarative.cpp -o cfgtest_QtDeclarative -L/usr/lib -Wl,-O1 -lQtDeclarative Checking to see if the QtOpenGL module should be built... g++ -DQT_NO_DEBUG -DQT_OPENGL_LIB -DQT_CORE_LIB -I. -I/usr/mkspecs/linux-g++ -I/usr/include/qt4/QtOpenGL -I/usr/include/qt4/QtCore -I/usr/include/qt4 -I/usr/X11R6/include -pipe -Os -w -D_REENTRANT cfgtest_QtOpenGL.cpp -o cfgtest_QtOpenGL -L/usr/lib -L/usr/X11R6/lib -Wl,-O1 -lQtOpenGL -lQtCore Checking to see if the QtScript module should be built... g++ -DQT_NO_DEBUG -DQT_SCRIPT_LIB -I. -I/usr/mkspecs/linux-g++ -I/usr/include/qt4/QtScript -I/usr/include/qt4 -pipe -Os -w -D_REENTRANT cfgtest_QtScript.cpp -o cfgtest_QtScript -L/usr/lib -Wl,-O1 -lQtScript Checking to see if the QtScriptTools module should be built... g++ -DQT_NO_DEBUG -DQT_SCRIPTTOOLS_LIB -I. -I/usr/mkspecs/linux-g++ -I/usr/include/qt4/QtScriptTools -I/usr/include/qt4 -pipe -Os -w -D_REENTRANT cfgtest_QtScriptTools.cpp -o cfgtest_QtScriptTools -L/usr/lib -Wl,-O1 -lQtScriptTools Checking to see if the QtSql module should be built... g++ -DQT_NO_DEBUG -DQT_SQL_LIB -I. -I/usr/mkspecs/linux-g++ -I/usr/include/qt4/QtSql -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I/usr/X11R6/include -pipe -Os -w -D_REENTRANT cfgtest_QtSql.cpp -o cfgtest_QtSql -L/usr/lib -L/usr/X11R6/lib -Wl,-O1 -lQtSql -lQtGui Checking to see if the QtSvg module should be built... g++ -DQT_NO_DEBUG -I. -I/usr/mkspecs/linux-g++ -I/usr/include/qt4/QtSvg -I/usr/include/qt4 -pipe -Os -w -D_REENTRANT cfgtest_QtSvg.cpp -o cfgtest_QtSvg -L/usr/lib -Wl,-O1 -lQtSvg Checking to see if the QtTest module should be built... g++ -DQT_NO_DEBUG -DQT_TEST_LIB -I. -I/usr/mkspecs/linux-g++ -I/usr/include/qt4/QtTest -I/usr/include/qt4 -pipe -Os -w -D_REENTRANT cfgtest_QtTest.cpp -o cfgtest_QtTest -L/usr/lib -Wl,-O1 -lQtTest Checking to see if the QtWebKit module should be built... g++
[PyQt] Going back through old bugs ...
As I've mentioned previously, I'm gradually looking at old PyQt bugs in Debian and Ubuntu and reviewing them. Looking at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=523149 it seems to be a user misunderstanding the API. It seems this might have been due to unclear documentation, so I thought it worth forwarding for review. Scott K ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Segfault when the dbus connection is lost
Phil Thompson p...@riverbankcomputing.com wrote: On Fri, 13 Apr 2012 11:52:31 -0300, Alejandro J. Cura al...@canonical.com wrote: Hi, first of all, since I'm new to the list I'd like to thank the people responsible for PyQt a lot for making such a great project. I'd like to report a bug: when using DBusQtMainLoop, I'm getting SIGSEGVs when the DBus connection is closed. I've managed to reproduce this from Ubuntu Lucid (PyQt 4.7.2) up to Ubuntu Precise beta 2 (PyQt 4.9.1). Attached is a script that when ran shows the issue, but not every time; on my Precise machine it happens about 3 out of 10 times; on a Lucid VM it happens every time. Please let me know if I should attach any other info, or if there's some simple way to fix it that I'm missing. BTW: I've seen this bug reported elsewhere[0] for projects using PyQt, but I'm not sure where I should report it for PyQt. thanks! Should be fixed in tonight's PyQt snapshot. I suspect I will be able to figure it out by diffing the two snapshots, but I'd appreciate it if you would provide the patch that fixes this so we can apply it to the current release. Ubuntu is very close to release, so they aren't in a position to wait for the next PyQt release. Scott K ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Segfault when the dbus connection is lost
On Saturday, April 14, 2012 06:16:00 PM Phil Thompson wrote: On Sat, 14 Apr 2012 13:07:58 -0400, Scott Kitterman deb...@kitterman.com wrote: Phil Thompson p...@riverbankcomputing.com wrote: On Fri, 13 Apr 2012 11:52:31 -0300, Alejandro J. Cura al...@canonical.com wrote: Hi, first of all, since I'm new to the list I'd like to thank the people responsible for PyQt a lot for making such a great project. I'd like to report a bug: when using DBusQtMainLoop, I'm getting SIGSEGVs when the DBus connection is closed. I've managed to reproduce this from Ubuntu Lucid (PyQt 4.7.2) up to Ubuntu Precise beta 2 (PyQt 4.9.1). Attached is a script that when ran shows the issue, but not every time; on my Precise machine it happens about 3 out of 10 times; on a Lucid VM it happens every time. Please let me know if I should attach any other info, or if there's some simple way to fix it that I'm missing. BTW: I've seen this bug reported elsewhere[0] for projects using PyQt, but I'm not sure where I should report it for PyQt. thanks! Should be fixed in tonight's PyQt snapshot. I suspect I will be able to figure it out by diffing the two snapshots, but I'd appreciate it if you would provide the patch that fixes this so we can apply it to the current release. Ubuntu is very close to release, so they aren't in a position to wait for the next PyQt release. Scott K Attached. Why wasn't the bug (which is 5 years old) not reported upstream earlier? Thanks for the quick turnaround. I've only recently started helping with PyQt maintenance, primarily in Debian, but also some in Ubuntu. It was initially reported as a PyKDE bug. Personally, I'm working my way through old bugs to try and get things caught up, but with some of them it's really hard to know which ones are still valid. It was reported now because Alejandro had come up with a reduced test case and I encouraged him to join the list and report it. Scott K ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
[PyQt] Fwd: Bug#667910: python-qt4: Raises underlying C/C++ object has been deleted while it has not been created
Forwarding this suggestion from a Debian user. Scott K -- Forwarded Message -- Subject: Bug#667910: python-qt4: Raises underlying C/C++ object has been deleted while it has not been created Date: Saturday, April 07, 2012, 03:15:19 PM From: Valentin Lorentz prog...@progval.net To: sub...@bugs.debian.org Package: python-qt4 Version: 4.9.1-1 Severity: wishlist Tags: upstream Hi, When you subclass a QObject, overwrite the constructor, and forget to call super(MyClass, self).__init__(), you get this error: RuntimeError: underlying C/C++ object has been deleted However, in this case, we get it because the object has not even been created, so I think you should add another message for that (it took me some time to figure out why I was getting this error). Regards, Valentin Lorentz -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages python-qt4 depends on: ii libc6 2.13-27 ii libgcc1 1:4.7.0-1 ii libpython2.7 2.7.3~rc2-1 ii libqt4-dbus 4:4.7.4-3 ii libqt4-declarative4:4.7.4-3 ii libqt4-designer 4:4.7.4-3 ii libqt4-help 4:4.7.4-3 ii libqt4-network4:4.7.4-3 ii libqt4-script 4:4.7.4-3 ii libqt4-scripttools4:4.7.4-3 ii libqt4-svg4:4.7.4-3 ii libqt4-test 4:4.7.4-3 ii libqt4-xml4:4.7.4-3 ii libqt4-xmlpatterns4:4.7.4-3 ii libqtassistantclient4 4.6.3-3 ii libqtcore44:4.7.4-3 ii libqtgui4 4:4.7.4-3 ii libqtwebkit4 2.2.0-3 ii libstdc++64.7.0-1 ii python2.7.2-10 ii python-sip [sip-api-8.1] 4.13.2-1 ii python2.6 2.6.7-4 ii python2.7 2.7.3~rc2-1 python-qt4 recommends no packages. Versions of packages python-qt4 suggests: pn python-qt4-dbg none -- no debconf information - ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
[PyQt] Fwd: Bug#661854: python-qt4: segfault calling family() on QFontInfo object
This is a user reported bug. I get the same segmentation fault. I tried the sample program with 4.8.5 and 4.9.1 (both python and python3) on Debian and Ubuntu with the same results. Scott K -- Forwarded Message -- Subject: Bug#661854: python-qt4: segfault calling family() on QFontInfo object Date: Friday, March 02, 2012, 12:06:17 AM From: Yann Dirson ydir...@free.fr To: Debian Bug Tracking System sub...@bugs.debian.org Package: python-qt4 Version: 4.9.1-1 Severity: normal $ python Python 2.7.2+ (default, Nov 30 2011, 19:22:03) [GCC 4.6.2] on linux2 Type help, copyright, credits or license for more information. from PyQt4 import QtCore, QtGui, QtSvg fi = QtGui.QFontInfo(QtGui.QFont()) fi PyQt4.QtGui.QFontInfo object at 0x7fbf89211b40 fi.family() Segmentation fault -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (101, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages python-qt4 depends on: ii libc6 2.13-26 ii libgcc1 1:4.6.2-12 ii libpython2.7 2.7.2-8 ii libqt4-dbus 4:4.7.4-2 ii libqt4-declarative4:4.7.4-2 ii libqt4-designer 4:4.7.4-2 ii libqt4-help 4:4.7.4-2 ii libqt4-network4:4.7.4-2 ii libqt4-script 4:4.7.4-2 ii libqt4-scripttools4:4.7.4-2 ii libqt4-svg4:4.7.4-2 ii libqt4-test 4:4.7.4-2 ii libqt4-xml4:4.7.4-2 ii libqt4-xmlpatterns4:4.7.4-2 ii libqtassistantclient4 4.6.3-3 ii libqtcore44:4.7.4-2 ii libqtgui4 4:4.7.4-2 ii libqtwebkit4 2.2.0-3 ii libstdc++64.6.2-12 ii python2.7.2-10 ii python-sip [sip-api-8.1] 4.13.2-1 ii python2.6 2.6.7-4 ii python2.7 2.7.2-8 - ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
[PyQt] Incompatibility between PyQt compiled with Qt 4.7 and 4.8
We've run into an issue in Ubuntu where we had Sip4 4.13.1and PyQt 4.9 built against Qt 4.7.4. PyKDE4 4.8.0 was built using this set of packages. All was working well. We rebuilt PyQt 4.9 against Qt 4.8.0 due to some packaging updates and had problems. The primary Ubuntu bug is: https://bugs.launchpad.net/ubuntu/+source/pykde4/+bug/922721 Rebuilding PyKDE4 with the newer PyQt package resolved the immediate issue, but leaves open the question of what caused the incompatiblity and what other packages might be affected. python -c import PyKDE4.kdecore was enough to replicate the problem. Suggestions? Scott K signature.asc Description: This is a digitally signed message part. ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Incompatibility between PyQt compiled with Qt 4.7 and 4.8
Luca Beltrame ei...@heavensinferno.net wrote: In data sabato 28 gennaio 2012 12:13:41, Scott Kitterman ha scritto: but leaves open the question of what caused the incompatiblity and what other packages might be affected. As far as I can see, SIP makes no ABI guarantees between versions, so that's the (unfortunate) side effect. What used to happen in KDE was to require the highest available SIP and PyQt at the time of release. I've upped the requirements for PyKDE4 to the latest SIP and PyQt in KDE's git master a while ago, but I didn't do so in the 4.8 branch because I thought I would need a go from the maintainer first: I've emailed Simon, yes, but I didn't get a response. I'm not sure how that helps in this case because what changed was the Qt version used at compile time. The Sip4 PyQt versions were unchanged. Scott K ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Incompatibility between PyQt compiled with Qt 4.7 and 4.8
Andreas Pakulat ap...@gmx.de wrote: On 28.01.12 13:01:28, Scott Kitterman wrote: Luca Beltrame ei...@heavensinferno.net wrote: In data sabato 28 gennaio 2012 12:13:41, Scott Kitterman ha scritto: but leaves open the question of what caused the incompatiblity and what other packages might be affected. As far as I can see, SIP makes no ABI guarantees between versions, so that's the (unfortunate) side effect. What used to happen in KDE was to require the highest available SIP and PyQt at the time of release. I've upped the requirements for PyKDE4 to the latest SIP and PyQt in KDE's git master a while ago, but I didn't do so in the 4.8 branch because I thought I would need a go from the maintainer first: I've emailed Simon, yes, but I didn't get a response. I'm not sure how that helps in this case because what changed was the Qt version used at compile time. The Sip4 PyQt versions were unchanged. Thats not what you said in your initial mail, you said that you rebuilt PyQt 4.9 against Qt 4.8, so of course the ABI of PyQt 4 might have changed due to that, requiring a rebuild of PyKDE4. Sorry I wasn't clear. I was trying to communicate that the PyQt ABI changes depending on what Qt it is compiled with. Scott K ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] PyQt4 fails to build dbus.mainloop.qt extension with Python 3
On Sunday, January 29, 2012 05:00:44 AM Arfrever Frehtes Taifersar Arahesis wrote: 2012-01-27 11:42:04 Phil Thompson napisał(a): Try tonight's PyQt snapshot - completely untested. dbus.cpp: In function ‘dbus_bool_t add_watch(DBusWatch*, void*)’: dbus.cpp:39:14: warning: ‘int dbus_watch_get_fd(DBusWatch*)’ is deprecated (declared at /usr/include/dbus-1.0/dbus/dbus-connection.h:450) dbus.cpp:39:37: warning: ‘int dbus_watch_get_fd(DBusWatch*)’ is deprecated (declared at /usr/include/dbus-1.0/dbus/dbus-connection.h:450) dbus.cpp: In function ‘void remove_watch(DBusWatch*, void*)’: dbus.cpp:72:14: warning: ‘int dbus_watch_get_fd(DBusWatch*)’ is deprecated (declared at /usr/include/dbus-1.0/dbus/dbus-connection.h:450) dbus.cpp:72:37: warning: ‘int dbus_watch_get_fd(DBusWatch*)’ is deprecated (declared at /usr/include/dbus-1.0/dbus/dbus-connection.h:450) dbus.cpp: In function ‘void toggle_watch(DBusWatch*, void*)’: dbus.cpp:104:14: warning: ‘int dbus_watch_get_fd(DBusWatch*)’ is deprecated (declared at /usr/include/dbus-1.0/dbus/dbus-connection.h:450) dbus.cpp:104:37: warning: ‘int dbus_watch_get_fd(DBusWatch*)’ is deprecated (declared at /usr/include/dbus-1.0/dbus/dbus-connection.h:450) dbus.cpp: In function ‘PyObject* DBusQtMainLoop(PyObject*, PyObject*, PyObject*)’: dbus.cpp:344:51: warning: deprecated conversion from string constant to ‘char*’ dbus.cpp: In function ‘PyObject* PyInit_qt()’: dbus.cpp:408:5: warning: missing initializer for member ‘PyModuleDef_Base::m_init’ dbus.cpp:408:5: warning: missing initializer for member ‘PyModuleDef_Base::m_index’ dbus.cpp:408:5: warning: missing initializer for member ‘PyModuleDef_Base::m_copy’ dbus.cpp:408:5: warning: missing initializer for member ‘PyModuleDef::m_reload’ dbus.cpp:408:5: warning: missing initializer for member ‘PyModuleDef::m_traverse’ dbus.cpp:408:5: warning: missing initializer for member ‘PyModuleDef::m_clear’ dbus.cpp:408:5: warning: missing initializer for member ‘PyModuleDef::m_free’ dbus.cpp:413:9: error: return-statement with no value, in function returning ‘PyObject*’ make[1]: *** [dbus.o] Error 1 The Ubuntu patch that Jonathan Riddell mentioned at least compiles. You might give that a try. Scott K ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
