[MacPorts] #64312: iaito: ld: cannot link directly with dylib/framework, your binary is not an allowed client of /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks//Python.framework/Python.tbd

[MacPorts]

#64312: iaito: ld: cannot link directly with dylib/framework, your binary is not an
allowed client of
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks//Python.framework/Python.tbd
-------------------------+------------------------
  Reporter:  ryandesign  |      Owner:  i0ntempest
      Type:  defect      |     Status:  assigned
  Priority:  Normal      |  Milestone:
 Component:  ports       |    Version:  2.7.1
Resolution:              |   Keywords:
      Port:  iaito       |
-------------------------+------------------------

Comment (by ryandesign):

 Yes, that would be the question!

 I see in the build log the following flags:

 {{{
 -F/opt/local/Library/Frameworks ...
 -F/opt/local/Library/Frameworks/Python.framework -framework Python
 }}}

 `-framework Python` would mean "link with the first Python.framework found
 in all of the Frameworks directories".

 `-F/opt/local/Library/Frameworks` would mean "look for frameworks in
 /opt/local/Library/Frameworks". There is a Python.framework in there,
 however it has many versions. Which version would it use? As far as know,
 it uses whichever one the Current symlink points to. MacPorts doesn't
 provide a Current symlink within the Python.framework so I think
 effectively that means this Python.framework is not found.

 `-F/opt/local/Library/Frameworks/Python.framework` would mean "look for
 frameworks in /opt/local/Library/Frameworks/Python.framework" which makes
 no sense since there aren't any frameworks within the Python.framework.
 Therefore this flag doesn't do anything useful.

 The Python.framework that `-framework Python` finds, then, must be the
 system one.

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