[MacPorts] #62309: Macports 2.6.4_1 requires SDK 11.2

[MacPorts]

#62309: Macports 2.6.4_1 requires SDK 11.2
----------------------+--------------------
  Reporter:  robwgla  |      Owner:  (none)
      Type:  defect   |     Status:  new
  Priority:  Normal   |  Milestone:
 Component:  base     |    Version:
Resolution:           |   Keywords:
      Port:           |
----------------------+--------------------

Comment (by kencu):

 I am not sure how else to explain it.

 MacPorts base checks your system, sees it is 11.2, so uses that number to
 look for an SDK to use: MacOSX11.2.sdk.

 But there is no such thing as a MacOSX11.2.sdk. It is phantom, a vapour,
 an imagination -- it doesn't exist yet.

 It's a (minor) screw up in base, with the assumption that there would
 ALWAYS be an SDK matching the system version number. But there is no such
 SDK. So base warns you that there is no such SDK (this is -- really --
 your problem I guess because no warning, no confusion about the warning --
 but I digress).

 And then base looks next for the next option in the line, which is the
 MacOSX.sdk, which exists, and so uses that, and away you go, building.

 But at some later time, something causes you to have a build error, You
 have no idea what it is. But you remember that warning (helpful warning)
 that there was no MacOSX11.2.sdk and you think ===> "That's It!".

 But that is Not It.

 What it actually is, nobody knows, because we have no ticket for the
 error, and no log to see what went wrong.

 So we keep talking about the SDK (non) issue, which (probably) has
 absolutely nothing to do with whatever is making your build fail.

 (Which is likely going to be a problem with gcc's baked-in SDK path, but
 we don't know that yet.)

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