#55329 closed defect (fixed)
py35-pyqt4 build failure
Reported by: | dyne2meter | Owned by: | michaelld (Michael Dickens) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.4.2 |
Keywords: | Cc: | ccorn | |
Port: | py-pyqt4 |
Description
Mavericks, 10.9.5. Log attached.
Attachments (1)
Change History (8)
Changed 7 years ago by dyne2meter
Attachment: | pyqt.log.gz added |
---|
comment:1 Changed 7 years ago by mf2k (Frank Schima)
Owner: | set to michaelld |
---|---|
Port: | py-pyqt4 added; py35-pyqt4 4.12.1_1 removed |
Status: | new → assigned |
In the future, please Cc the port maintainers (port info --maintainers py35-pyqt4
), if any.
comment:2 Changed 7 years ago by michaelld (Michael Dickens)
Is the py35 version required, or can you move to py36? Does the py36 version also not build for you?
comment:3 Changed 7 years ago by 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.
comment:4 Changed 7 years ago by ccorn
Cc: | ccorn added |
---|
comment:5 Changed 7 years ago by 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. Edit: Already done.
comment:6 Changed 7 years ago by michaelld (Michael Dickens)
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
OK; well great I'll go ahead and close as fixed, even if indirectly.
comment:7 Changed 7 years ago by dyne2meter
Sounds good to me. Whatever was done has eliminated the issue for me, too.
Note: See
TracTickets for help on using
tickets.
build log