I just wanted to bring some closure to my old thread in case someone browses the archive:
Following Brian's suggestion of editing PyQt-*-4.9.1/sip/QtNetwork/qssl.sip as explained in the following thread solved the configuration problem I had since December. I had given up then since nothing seemed to help and I had found a build online that had worked for my needs. Info can be found under the following thread, and it is my understanding that at this time a new snapshot is fixing the issue: [PyQt] sip: __or__() unsupported function return type - provide %MethodCode and a C++ signature ( QT 4.8.1 + PyQt 4.9.1 ). Cheers. nico On Thu, Apr 26, 2012 at 12:41 PM, Hans-Peter Jansen <h...@urpla.net> wrote: > Am Wednesday 25 April 2012 14:28:54 schrieb Brian Kelley: > > That would have been nice, except (1) This affected multiple distress > that > > did not have the openSUSE build service (2) I need to build with multiple > > pythons (2.3Š2.7) (3) I need to install into a specific prefix and PyQt > is > > not easily re-locatable and (4) I use the commercial distribution and > this > > affected ubuntu and SLED10. > > Hmm, (1, 4) did you notice the broad range of distros, that BS supports - > including various debian, ubuntu and SuSE commercial releases... > > (2) Building against various python distros is a matter of including that > python version within that project. > > (3) I usually do path tinkering in spec files with sed scripts without > modifying the source nor creating a patch. > > Finally, setting up a private BS is a bit of a hassle and non rpm based > packaging adds some complexity, though. > > You're free to do whatever you want of course - I just wanted to show some > interesting alternatives to the ordinary build from tarballs.. > > Pete > > > Brian > > > > >You could have spared a significant amount of your time by simply > > >building sip > > >and friends in openSUSEs build service. That typically results in > > >properly > > >installable packages, and a new target (distribution) is mostly a matter > > >of a > > >few clicks. There are plenty of packages/examples in BS, that could > serve > > >as > > >the rpm spec template (including mine found here: > > > https://build.opensuse.org/project/show?project=home%3Afrispete > > > http://download.opensuse.org/repositories/home:/frispete:/ > > >). > > > > > >Pete > > > > > >> Brian > > >> > > >> On 4/19/12 2:09 PM, "murison" <muri...@alpheratz.net> wrote: > > >> >I, too, am stopped cold by this very same problem. Sip 4.13.2, Python > > >> >2.7.3, > > >> >Qt 4.8.1, PyQt 4.9.1 on Ubuntu 11.10. > > >> > > > >> >-- > > >> >View this message in context: > > >>> > > >>> > http://python.6.n6.nabble.com/Cannot-configure-PyQt4-9-before-build-on-L > > >>>in > > >>> > > >> >uxmint-tp2309321p4899103.html > > >> >Sent from the PyQt mailing list archive at Nabble.com. > > >> >_______________________________________________ > > >> >PyQt mailing list PyQt@riverbankcomputing.com > > >> >http://www.riverbankcomputing.com/mailman/listinfo/pyqt > > > > _______________________________________________ > > PyQt mailing list PyQt@riverbankcomputing.com > > http://www.riverbankcomputing.com/mailman/listinfo/pyqt > > > _______________________________________________ > PyQt mailing list PyQt@riverbankcomputing.com > http://www.riverbankcomputing.com/mailman/listinfo/pyqt > -- "Attention, attention. Here and now, boys," the mynah repeated. "Here and now, boys."
_______________________________________________ PyQt mailing list PyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
