py35-pyqt4 build failure

[dyne2meter]

Mavericks, 10.9.5. Log attached.

[dyne2meter]

build log

[mf2k (Frank Schima)]

In the future, please Cc the port maintainers (port info --maintainers py35-pyqt4), if any.

[michaelld (Michael Dickens)]

Is the py35 version required, or can you move to py36? Does the py36 version also not build for you?

[michaelld (Michael Dickens)]

Looks like this is the same basic issue as #55250, just for py35 instead of py27. I saw a fix somewhere. Will try to track it down.

[ccorn]

This seems to have been ​due to SIP (commit ​dd017d3e1454). Upgrading port py-sip to 4.19.6 has fixed this issue for me.

--- a/python/py-sip/Portfile
+++ b/python/py-sip/Portfile
@@ -20,7 +20,7 @@ long_description \
 
 homepage            http://www.riverbankcomputing.co.uk/software/sip/intro
 
-version             4.19.5
+version             4.19.6
 
 # from siplib/sip.h.in:
 #
@@ -59,8 +59,8 @@ if {${name} ne ${subport}} {
         distname        sip-${version}
     }
 
-    checksums           rmd160 d7b2b3bfd8f350c6be1d6bfe9d3761ad1cb73320 \
-                        sha256 391b7bf08f1cd12d8a25ed5608ca36ee9b759eee1690d8156e35d92f9a74b456
+    checksums           rmd160 8cff31053f90efb30633e78e6beadb6dd351300a \
+                        sha256 9dda27ae181bea782ebc8768d29f22f85ab6e5128ee3ab21f491febad707925a
 
     patchfiles          patch-siputils.py.diff \
                         patch-specs_macx-g++.diff \

[michaelld (Michael Dickens)]

OK; well great I'll go ahead and close as fixed, even if indirectly.

[dyne2meter]

Sounds good to me. Whatever was done has eliminated the issue for me, too.