!aGqRytqbCECitOFhbt:nixos.org

Release Management

340 Members
25.11 "Xantusia" | https://nixos.github.io/release-wiki/Home.html93 Servers

You have reached the beginning of time (for this room).


SenderMessageTime
11 Apr 2024
@wegank:matrix.orgWeijiaWe're almost -7 weeks from release, so probably should start the first event asap04:12:02
@jonringer:matrix.orgjonringerI was expecting to go through 4.1 and 4.2 together https://nixos.github.io/release-wiki/Once-Appointed.html04:14:25
@jonringer:matrix.orgjonringera lot of the "work" is pretty "copy, update, paste". If you feel confident to do it on your own, feel free to do so. Otherwise we go through it together04:16:06
@jonringer:matrix.orgjonringer * a lot of the "work" is pretty "copy, update, paste". If you feel confident to do it on your own, feel free to do so. Otherwise we can go through it together 04:16:26
@wegank:matrix.orgWeijiaFeature freeze announcement: https://github.com/NixOS/nixpkgs/issues/30328606:17:47
@reckenrode:matrix.orgRandy EckenrodeI assume cctools/ld64 would fall under binutils. Where does bumping the effective minimum version on Darwin fall on the breaking scale? The cctools/ld64 update may require a bump to 10.14 as the effective minimum version for building things.16:09:22
@wegank:matrix.orgWeijia
In reply to @reckenrode:matrix.org
I assume cctools/ld64 would fall under binutils. Where does bumping the effective minimum version on Darwin fall on the breaking scale? The cctools/ld64 update may require a bump to 10.14 as the effective minimum version for building things.
I think I'd ask for an x86_64-darwin jobset (and a public announcement) before approving a PR on this, even if it only contains a treewide substitution of "10.12" by "10.14"
16:47:08
@jonringer:matrix.orgjonringer10.14 is kind of "big" for macOS, C++14 (IIRC), and a few other tooling improvements landed in that release16:48:48
@jonringer:matrix.orgjonringerHowever, it was released in Sept 2018, so I think ~5 years is a pretty low bar16:49:20
@reckenrode:matrix.orgRandy Eckenrode
In reply to @wegank:matrix.org
I think I'd ask for an x86_64-darwin jobset (and a public announcement) before approving a PR on this, even if it only contains a treewide substitution of "10.12" by "10.14"
It’s not an SDK change. That will come post 24.05. The updated cctools and ld64 have a hard requirement on using libdispatch APIs that are only available in 10.14. They can be built with the 11.0 SDK and a 10.14 deployment target in the meantime until the default SDK is changed.
16:49:37
@reckenrode:matrix.orgRandy Eckenrode
In reply to @jonringer:matrix.org
10.14 is kind of "big" for macOS, C++14 (IIRC), and a few other tooling improvements landed in that release
We use our own libc++, so even 10.12 has whatever the latest is. This ld64 update would bring Darwin up to the version of ld-classic shipped in Xcode 15.3. The cctools update handles signatures better. If it’s a linker-signed ad hoc signature, strip&c will update the signature automatically without a hook or wrapper.
16:52:12
@wegank:matrix.orgWeijia
In reply to @reckenrode:matrix.org
It’s not an SDK change. That will come post 24.05. The updated cctools and ld64 have a hard requirement on using libdispatch APIs that are only available in 10.14. They can be built with the 11.0 SDK and a 10.14 deployment target in the meantime until the default SDK is changed.
Wait, with the 11.0 SDK on x86_64-darwin?
16:52:18
@reckenrode:matrix.orgRandy Eckenrode
In reply to @wegank:matrix.org
Wait, with the 11.0 SDK on x86_64-darwin?
Yes. overrideSDK can build with one SDK and set an earlier deployment target. Fixing that was one of the goals of the rewrite in staging.
16:53:10

Show newer messages


Back to Room ListRoom Version: 6