[MacPorts] #69697: Error: Failed to configure mpv: no files matched glob pattern "MacOSX*.sdk"

[MacPorts]

#69697: Error: Failed to configure mpv: no files matched glob pattern "MacOSX*.sdk"
---------------------+----------------------
  Reporter:  jf      |      Owner:  Ionic
      Type:  defect  |     Status:  assigned
  Priority:  Normal  |  Milestone:
 Component:  ports   |    Version:
Resolution:          |   Keywords:
      Port:  mpv     |
---------------------+----------------------

Comment (by jf):

 Replying to [comment:13 kencu]:
 > That block of code is in the Portfile now.
 >
 > https://github.com/macports/macports-
 ports/blob/74fd7cf10be3cd8008ec9b61fd9203d5472c620e/multimedia/mpv/Portfile#L166
 >
 > Apparently it does work (in the default situation) to find the
 MacOSX.sdk in the SDKs folder. It's non-standard code. I don't know why it
 is needed. Most ports don't need to use code like this to specify the SDK.
 But this port uses this code for some reason.
 >
 > Eyeballing it, it looks like it should work. Yet it doesn't work in your
 setup.
 >
 > So what is different about your setup? -- what are the permissions set
 like in your home folder?  Are you dealing with any symlinks or other
 unusual redirects that might break the code?
 >
 > To sort that out you perhaps would start sprinkling "puts" in the code
 to see what the variables are really being set to, just like back in the
 1980s when we would debug code with "printf" statements to see what is
 going on with it.
 >
 > Somehow, somewhere, that "glob" is not "globbing" the SDK from that
 directory, when apparently it should be globbing it.
 >
 > But there is not enough informaiton here to have an idea why not.

 thank you, and I appreciate the explanation. My question was actually
 about how to locate the portfile in the first place so I can modify it for
 testing; and then after, to install using it.

 But regardless, thank you again! the permissions question is indeed the
 right path. I had chmod 700-ed my home directory. I definitely wasn't
 expecting that this would be an issue with macports, given that I run with
 `sudo`... but that was the issue.

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