[MacPorts] #62475: py-pyobjc @7.1_0: Symbol not found: _ffi_find_closure_for_code_np

[MacPorts]

#62475: py-pyobjc @7.1_0: Symbol not found: _ffi_find_closure_for_code_np
------------------------+--------------------
  Reporter:  dsedivec   |      Owner:  danchr
      Type:  defect     |     Status:  closed
  Priority:  Normal     |  Milestone:
 Component:  ports      |    Version:  2.6.4
Resolution:  fixed      |   Keywords:
      Port:  py-pyobjc  |
------------------------+--------------------
Changes (by danchr):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"217d8731dcc6247f67004de48d3f4760b07e33db/macports-ports"
 217d8731dcc6247f67004de48d3f4760b07e33db/macports-ports] (master):
 {{{
 #!ConfigurableCommitTicketReference repository="macports-ports"
 revision="217d8731dcc6247f67004de48d3f4760b07e33db"
 py-pyobjc: don't use MacPorts libffi on Big Sur

 PyObjC requires changes to libffi which Apple has yet to merge into
 upstream. The build system incorrectly picked up the headers for the
 system libffi, yet linked against MacPorts libffi, generating a binary
 that failed with an error on load.

 This fixes that by forcing use of the system-provided libffi on Big
 Sur, and adjusts patches the sources to use the correct headers
 elswehere. As libffi is a dependency of CPython itself, merely
 removing it from the list of dependencies doesn't suffice, and we have
 to include it by path.

 While at it, I've applied some patches to force setuptools so that we
 can build in parallel.

 Fixes: https://trac.macports.org/ticket/62475
 }}}

-- 
Ticket URL: <https://trac.macports.org/ticket/62475#comment:9>
MacPorts <https://www.macports.org/>
Ports system for macOS