Changes between Initial Version and Version 1 of Ticket #48233


Ignore:
Timestamp:
Jul 3, 2015, 6:33:11 AM (9 years ago)
Author:
ryandesign (Ryan Carsten Schmidt)
Comment:

Did you get a binary from our packages server, or build py34-cairo from source? I suspect you got a binary. I suspect py-cairo builds itself differently depending on whether cairo has x11 support or not. Therefore, py-cairo should have an x11 variant, and use the require_active_variants procedure in the active_variants 1.1 portgroup to ensure a match between the variants of the py-cairo subports and the cairo port. That is what was done in r100265 to fix #34889. It was undone in r129111; see #38606. The removal of this code appears to have been incorrect and it or something like it should be reinstated.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #48233

    • Property Cc jeremyhu@… added; sean openmaintainer removed
    • Property Owner changed from macports-tickets@… to sean@…

  • Ticket #48233 – Description

    initial v1  
    1 Might be related to [https://trac.macports.org/ticket/34889 #34889] or [https://trac.macports.org/ticket/34724 #34724].
     1Might be related to #34889 or #34724.
    22
    33My cairo @1.14.2_1+quartz is built without x11 support, and I added py34-cairo @1.10.0_3 just now. However, when I then try to load cairo from Python, loading the library fails with what I suspect is a missing x11 symbol: