Hi All, Just a warning that following the macOS 11.1 update (and corresponding Xcode 12.3) the SDK version has indeed changed from 11.0 to 11.1
Oberon ~/Projects/MacPorts/base > ls
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs
DriverKit20.2.sdk MacOSX.sdk MacOSX11.1.sdk
Oberon ~/Projects/MacPorts/base > ls /Library/Developer/CommandLineTools/SDKs/
MacOSX.sdk MacOSX10.15.sdk MacOSX11.1.sdk
This causes problems, as there appears to be places in base that assume the SDk
would always be 11.0 for all Big Sur, macOS11 releases, e.g.
Oberon ~/Projects/MacPorts/ports > sudo port -s -v configure root6
Warning: The macOS 11.0 SDK does not appear to be installed. Ports may not
build correctly.
Warning: You can install it as part of the Xcode Command Line Tools package by
running `xcode-select --install’.
I haven’t checked in detail, but at least
https://github.com/macports/macports-base/blob/6c1396fd48a85c71cda98bc169f95561e07d1eda/src/macports1.0/macports.tcl#L1157
<https://github.com/macports/macports-base/blob/6c1396fd48a85c71cda98bc169f95561e07d1eda/src/macports1.0/macports.tcl#L1157>
https://github.com/macports/macports-base/blob/6c1396fd48a85c71cda98bc169f95561e07d1eda/src/macports1.0/macports.tcl#L1164
<https://github.com/macports/macports-base/blob/6c1396fd48a85c71cda98bc169f95561e07d1eda/src/macports1.0/macports.tcl#L1164>
are two places that need fixing.
As I guess people running macOS11 are likely to update to 11.1, we should
probably look to fixing this quite quickly.
Chris
smime.p7s
Description: S/MIME cryptographic signature
