On 2020-8-28 07:12 , Ryan Schmidt wrote: > > >> On Aug 27, 2020, at 14:55, Jason Liu wrote: >> >> Yes, I see what you're talking about now. And since I've only used machines >> that had a single SDK installed, I've never encountered this problem. >> >> As far as I can tell, the value of configure.sdkroot is empty > > That is the case sometimes, such as when the version of the SDK that MacPorts > wants is not available in the installed version of Xcode.
It should never be the case on 10.14 and later though. Even if there's no SDK matching the chosen configure.sdk_version, it will fall back to MacOSX.sdk and a warning will be printed. So if configure.sdkroot is empty, something in the Portfile (or its included PortGroups) must be clearing it. - Josh
