[prev in list] [next in list] [prev in thread] [next in thread]
List: pykde
Subject: Re: [PyQt] Cannot 'configure' PyQt4.9 before build on Linuxmint
From: Nico Dufort <ndufort () gmail ! com>
Date: 2012-04-28 15:40:36
Message-ID: CAE9k4pcjBuT_OKE4Uvg5yH+8=OERAEem=GwVThhguXpq=4nbyg () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
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 <hpj@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" <murison@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."
[Attachment #5 (text/html)]
<div class="gmail_extra">I just wanted to bring some closure to my old thread in case \
someone browses the archive:</div><div class="gmail_extra"><br></div><div \
class="gmail_extra">Following Brian's suggestion of editing<span style> \
PyQt-*-4.9.1/sip/QtNetwork/</span><span style>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.</span></div>
<div class="gmail_extra"><span style><br></span></div><div class="gmail_extra"><span \
style>Info can be found under the following thread, and it is my understanding that \
at this time a new snapshot is fixing the issue: </span>[PyQt] sip: __or__() \
unsupported function return type - provide %MethodCode and a C++ signature ( QT 4.8.1 \
+ PyQt 4.9.1 ).</div>
<div class="gmail_extra"><br></div><div class="gmail_extra"><br></div><div \
class="gmail_extra">Cheers. nico</div><div class="gmail_extra"><br></div><div \
class="gmail_extra"><br><div class="gmail_quote">On Thu, Apr 26, 2012 at 12:41 PM, \
Hans-Peter Jansen <span dir="ltr"><<a href="mailto:hpj@urpla.net" \
target="_blank">hpj@urpla.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">Am Wednesday 25 April 2012 14:28:54 schrieb Brian Kelley:<br> \
<div>> That would have been nice, except (1) This affected multiple distress \
that<br> > did not have the openSUSE build service (2) I need to build with \
multiple<br> > pythons (2.3Å 2.7) (3) I need to install into a specific prefix and \
PyQt is<br> > not easily re-locatable and (4) I use the commercial distribution \
and this<br> > affected ubuntu and SLED10.<br>
<br>
</div>Hmm, (1, 4) did you notice the broad range of distros, that BS supports -<br>
including various debian, ubuntu and SuSE commercial releases...<br>
<br>
(2) Building against various python distros is a matter of including that<br>
python version within that project.<br>
<br>
(3) I usually do path tinkering in spec files with sed scripts without<br>
modifying the source nor creating a patch.<br>
<br>
Finally, setting up a private BS is a bit of a hassle and non rpm based<br>
packaging adds some complexity, though.<br>
<br>
You're free to do whatever you want of course - I just wanted to show some<br>
interesting alternatives to the ordinary build from tarballs..<br>
<br>
Pete<br>
<div><div><br>
> Brian<br>
><br>
> >You could have spared a significant amount of your time by simply<br>
> >building sip<br>
> >and friends in openSUSEs build service. That typically results in<br>
> >properly<br>
> >installable packages, and a new target (distribution) is mostly a matter<br>
> >of a<br>
> >few clicks. There are plenty of packages/examples in BS, that could \
serve<br> > >as<br>
> >the rpm spec template (including mine found here:<br>
> > <a href="https://build.opensuse.org/project/show?project=home%3Afrispete" \
target="_blank">https://build.opensuse.org/project/show?project=home%3Afrispete</a><br>
> > <a href="http://download.opensuse.org/repositories/home:/frispete:/" \
target="_blank">http://download.opensuse.org/repositories/home:/frispete:/</a><br> \
> >).<br> > ><br>
> >Pete<br>
> ><br>
> >> Brian<br>
> >><br>
> >> On 4/19/12 2:09 PM, "murison" <<a \
href="mailto:murison@alpheratz.net" target="_blank">murison@alpheratz.net</a>> \
wrote:<br> > >> >I, too, am stopped cold by this very same problem. Sip \
4.13.2, Python<br> > >> >2.7.3,<br>
> >> >Qt 4.8.1, PyQt 4.9.1 on Ubuntu 11.10.<br>
> >> ><br>
> >> >--<br>
> >> >View this message in context:<br>
> >>><br>
> >>><a href="http://python.6.n6.nabble.com/Cannot-configure-PyQt4-9-before-build-on-L" \
target="_blank">http://python.6.n6.nabble.com/Cannot-configure-PyQt4-9-before-build-on-L</a><br>
> >>>in<br>
> >>><br>
> >> >uxmint-tp2309321p4899103.html<br>
> >> >Sent from the PyQt mailing list archive at Nabble.com.<br>
> >> >_______________________________________________<br>
> >> >PyQt mailing list <a href="mailto:PyQt@riverbankcomputing.com" \
target="_blank">PyQt@riverbankcomputing.com</a><br> > >> ><a \
href="http://www.riverbankcomputing.com/mailman/listinfo/pyqt" \
target="_blank">http://www.riverbankcomputing.com/mailman/listinfo/pyqt</a><br> \
><br> > _______________________________________________<br>
> PyQt mailing list <a href="mailto:PyQt@riverbankcomputing.com" \
target="_blank">PyQt@riverbankcomputing.com</a><br> > <a \
href="http://www.riverbankcomputing.com/mailman/listinfo/pyqt" \
target="_blank">http://www.riverbankcomputing.com/mailman/listinfo/pyqt</a><br> <br>
<br>
_______________________________________________<br>
PyQt mailing list <a href="mailto:PyQt@riverbankcomputing.com" \
target="_blank">PyQt@riverbankcomputing.com</a><br> <a \
href="http://www.riverbankcomputing.com/mailman/listinfo/pyqt" \
target="_blank">http://www.riverbankcomputing.com/mailman/listinfo/pyqt</a><br> \
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- \
<br>"Attention, attention. Here and now, boys," the mynah repeated. \
"Here and now, boys."<br> </div>
_______________________________________________
PyQt mailing list PyQt@riverbankcomputing.com
http://www.riverbankcomputing.com/mailman/listinfo/pyqt
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic