!lheuhImcToQZYTQTuI:nixos.org

Nix on macOS

1167 Members
“There are still many issues with the Darwin platform but most of it is quite usable.” — http://yves.gnu-darwin.org189 Servers

Load older messages


SenderMessageTime
2 Dec 2025
@samasaur:matrix.orgsamasaurbut the gist is that TM uses the default band size for the sparsebundle and so the bundle caps at 16TB even though there is more storage on the actual sahre 01:12:46
@samasaur:matrix.orgsamasaur* but the gist is that TM uses the default band size for the sparsebundle and so the bundle caps at 16TB even though there is more storage on the actual share01:12:50
@samasaur:matrix.orgsamasaurah https://discussions.apple.com/thread/255972168?sortBy=rank01:13:02
@xoredg:matrix.orgxoredshould I even bother reporting this for them to bump to 4.22.6?01:13:06
@xoredg:matrix.orgxoredor are we past that?01:13:13
@samasaur:matrix.orgsamasauryou can work around it by manually creating the bundle01:13:14
@xoredg:matrix.orgxorednot sure I follow, it is capped at some amount per backup or in total01:14:35
@samasaur:matrix.orgsamasaurit's capped bc time machine uses bad settings to create the bundle01:14:58
@samasaur:matrix.orgsamasaurso in total per machine01:15:17
@xoredg:matrix.orgxoredoh ok01:15:38
@xoredg:matrix.orgxoredwell you shouldn't be having 16tb in a workstation regardless lol01:15:51
@xoredg:matrix.orgxored1st world problems01:15:55
@samasaur:matrix.orgsamasaurthough yours is showing up as a time machine destination and not a normal SMB share, so i think you'd avoid this issue01:16:08
@samasaur:matrix.orgsamasaurim not sure how you accomplished that, i tried some things and couldn't figure it out01:16:35
@samasaur:matrix.orgsamasauroh wait nvm, that's not the time machine icon01:16:49
@samasaur:matrix.orgsamasaurthe tahoe ones all look so similar...01:17:00
@xoredg:matrix.orgxoredhmm I just did the avahi thing01:20:33
@reckenrode:matrix.orgRandy EckenrodeSwift Build requires the 15.x SDK because of course it does. 😞01:33:16
@reckenrode:matrix.orgRandy Eckenrode

swiftpm>     /nix/store/v86inqkxp9l2hk5z3laa6mlzpn8877y1-apple-sdk-15.5/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/lib/swift/_Concurrency.swiftmodule/arm64e-apple-macos.swiftinterface:29:40: error: macros are not supported in this compiler
swiftpm>     @freestanding(expression) public macro isolation<T>() -> T = Builtin.IsolationMacro
swiftpm>                                            ^
swiftpm>     /nix/store/v86inqkxp9l2hk5z3laa6mlzpn8877y1-apple-sdk-15.5/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/lib/swift/_Concurrency.swiftmodule/arm64e-apple-macos.swiftinterface:4439:72: error: macros are not supported in this compiler
swiftpm>     @attached(accessor) @attached(peer, names: prefixed(`$`)) public macro TaskLocal() = #externalMacro(module: "SwiftMacros", type: "TaskLocalMacro")
01:39:39
@reckenrode:matrix.orgRandy Eckenrode *
swiftpm>     /nix/store/v86inqkxp9l2hk5z3laa6mlzpn8877y1-apple-sdk-15.5/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/lib/swift/_Concurrency.swiftmodule/arm64e-apple-macos.swiftinterface:29:40: error: macros are not supported in this compiler
swiftpm>     @freestanding(expression) public macro isolation<T>() -> T = Builtin.IsolationMacro
swiftpm>                                            ^
swiftpm>     /nix/store/v86inqkxp9l2hk5z3laa6mlzpn8877y1-apple-sdk-15.5/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/lib/swift/_Concurrency.swiftmodule/arm64e-apple-macos.swiftinterface:4439:72: error: macros are not supported in this compiler
swiftpm>     @attached(accessor) @attached(peer, names: prefixed(`$`)) public macro TaskLocal() = #externalMacro(module: "SwiftMacros", type: "TaskLocalMacro")
01:39:49
@reckenrode:matrix.orgRandy Eckenrode Great. The 15.5 SDK has the TaskLocal change. 01:39:59
@emilazy:matrix.orgemilyhow is it defined in the 14.x SDK?01:52:07
@emilazy:matrix.orgemilyhttps://github.com/swiftlang/swift/pull/70902#pullrequestreview-183318911001:53:17
@emilazy:matrix.orgemilyfwiw, it looks like it was an issue for Android too.01:53:23
@emilazy:matrix.orgemilyand it's now conditional https://github.com/swiftlang/swift/commit/8d67a3723146c417a1986febfb207d1fe962a0d801:54:11
@emilazy:matrix.orgemilyperhaps a later version of the SDK will pick that up?01:54:19
@emilazy:matrix.orgemily (maybe not, if the .swiftinterface is after that) 01:55:46
@reckenrode:matrix.orgRandy EckenrodeIt’s a property wrapper. They changed it to a macro in Swift 6.0.01:56:07
@reckenrode:matrix.orgRandy Eckenrodehttps://github.com/swiftlang/swift/blame/36a3c6e61101419f4557781da79f291445cdfa1b/stdlib/public/Concurrency/TaskLocal.swift#L17-L3001:58:03
@emilazy:matrix.orgemily

I wonder if building against the version of the libraries in the Swift sources rather than using the SDK for the bootstrap would solve it – since the conditional is there in the source. alternatively –

shion:~/Developer/swift  (empty) (no description set)
❭ rg macro_unsupported
include/swift/AST/DiagnosticsSema.def
8083:ERROR(macro_unsupported,none,

lib/Sema/TypeCheckMacros.cpp
247:  macro->diagnose(diag::macro_unsupported);
1253:    ctx.Diags.diagnose(loc, diag::macro_unsupported);
1616:    attachedTo->diagnose(diag::macro_unsupported);
1761:                       diag::macro_unsupported);

lib/Sema/TypeCheckDeclPrimary.cpp
1189:  ctx.Diags.diagnose(initExpr->getLoc(), diag::macro_unsupported);

I wonder what happens if you just make these emit a warning rather than an error.

01:58:18

Show newer messages


Back to Room ListRoom Version: 6