-
Notifications
You must be signed in to change notification settings - Fork 624
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
release: avoid setting __MAC_OS_X_VERSION_MAX_ALLOWED
?
#2767
Comments
Availability.h says:
But I don't know who is setting 13.1? (__MAC_15_0 is 150000)
|
This should have been the release job: "Merge pull request #2566 from AkihiroSuda/dev #3207": https://github.com/lima-vm/lima/actions/runs/10610486369/job/29408056766 It sets up the runner like:
And there are a lot of warnings in the build logs:
Is the problem here that the Lima rosetta cache needs to be invalidated when macOS/Xcode is updated? Or that Vz is somehow hard-coding the version it was built with as the max, when setting up the sharing?
https://github.com/Code-Hex/vz/blob/main/osversion.go // for macOS 14 API
#if __MAC_OS_X_VERSION_MAX_ALLOWED >= 140000
#define INCLUDE_TARGET_OSX_14 1
#else
#pragma message("macOS 14 API has been disabled")
#endif https://github.com/Code-Hex/vz/blob/main/virtualization_helper.h |
So we are supposed to get some reasonable default like: But for some reason, the build sets the max version to the same as the current sdk. EDIT: Apparently that is the default behaviour, as dictated by the Availability headers. So need to build on a newer SDK (for the new API), but with a lower minimum version (for the old OS). i.e. use the
|
The end goal here is to be able to use the same binary, for all the macOS versions. Verify by testing the "Darwin_macOS15" binaries on macOS 13, and they should work. Then revert: Note: Virtualization.framework requires macOS 11, Rosetta(Linux) requires macOS 13 |
Originally posted by @afbjorklund in #2753 (comment)
The text was updated successfully, but these errors were encountered: