Opened 3 years ago

Closed 3 years ago

Last modified 3 years ago

#62204 closed defect (duplicate)

big sur 11.2 + xcode 12.4 with macos SDK 11.1

Reported by: minusf Owned by:
Priority: Normal Milestone:
Component: base Version: 2.6.4
Keywords: bigsur Cc:
Port:

Description

hello. i am new here but i tried to do my research.

Recently big sur had a largish security update bumping it to 11.2. Since that time macports is helpfully telling me the "SDK 11.2 not found" message. Well, it cannot be found as Xcode 12.4 does not have it (i have removed and reinstalled command line tools multiple times):

% ls -1l /Library/Developer/CommandLineTools/SDKs
lrwxr-xr-x  1 root  wheel   14 Feb  2 01:37 MacOSX.sdk@ -> MacOSX11.1.sdk
drwxr-xr-x  8 root  wheel  256 Jul  9  2020 MacOSX10.15.sdk/
drwxr-xr-x  7 root  wheel  224 Nov 30 13:33 MacOSX11.1.sdk/

but ports won't have it cause sw_vers -productVersion returns 11.2

Now I am not a long term macos/Xcode user, but according to https://xcodereleases.com it seems to me that Xcode releases generally don't come with every single macos point releases' SDK... I imagine this is not the first time this has happened as most of Xcode 12.x shipped with 10.15.6 and 11.0...

I don't know what is the macports way to fix this discrepancy, and I could not find an easy way to override the sdk_version, or even if that is possible, and symlinking 11.1 -> 11.2 is normally asking for trouble when it comes to SDK's, libraries and API's. But right now I cannot build packages with macports.

I am somewhat baffled that this is not in any of the FAQ, documenatation, etc. Could someone help me out please?

Change History (6)

comment:1 Changed 3 years ago by minusf

Type: requestdefect

(changing to defect, cause i see now "requests" are something else)

comment:2 Changed 3 years ago by jmroot (Joshua Root)

Keywords: bigsur added; big sur sdk xcode removed
Resolution: duplicate
Status: newclosed
Version: 2.6.4

This is effectively the same problem as #61866, which is mostly fixed in master and will be in an upcoming release. In the meantime with 2.6.4, the warning should not actually prevent building ports, as MacPorts should fall back to using MacOSX.sdk.

comment:3 Changed 3 years ago by jmroot (Joshua Root)

It's also possible to add macosx_sdk_version 11.1 to macports.conf, which should suppress the warning, but you don't want to forget to remove it when the bug is fixed and a new SDK version is released.

comment:4 Changed 3 years ago by minusf

thank you for the cluestick. (that setting seems to be undocumented though.)

comment:5 Changed 3 years ago by jmroot (Joshua Root)

Yeah, it's undocumented because you shouldn't normally set it.

comment:6 Changed 3 years ago by jmroot (Joshua Root)

Component: portsbase
Note: See TracTickets for help on using tickets.