| 15 Dec 2025 |
 niklaskorz | no it's used for variadic args ffi on all platforms | 23:16:05 |
| niklaskorz | https://github.com/pypy/pypy/blob/376cb12babe6bc8f43a550d2981a322513be24de/rpython/rlib/clibffi.py#L502-L507 | 23:16:15 |
 emily | sounds like they should probably just bump their target again then | 23:17:27 |
| emily | it won't fail to build with Apple toolchain but the warnings will probably show | 23:17:57 |
| emily | I think this is the first time us setting that error has caught something | 23:18:24 |
| emily | albeit something irrelevant for us | 23:18:30 |
 Randy Eckenrode | It caught something in one of the source ports.
https://github.com/NixOS/nixpkgs/blob/master/pkgs/os-specific/darwin/apple-source-releases/system_cmds/patches/conditionalize-security-transition-shims.patch
| 23:19:59 |
| niklaskorz | after bumping it to 10.15 I hit the next one 😄 pthread_jit_write_protect_np requires 11+ | 23:22:13 |
| niklaskorz | but that is indeed only used on arm64 | 23:22:31 |
| niklaskorz | well for the nixpkgs fix I'd prefer to just remove the deployment target altogether, but I'll report it upstream | 23:24:17 |
| emily | they should probably either -Wno-... (e.g. with a local pragma), guard it, or pass 11.0 on AArch64 | 23:28:42 |
| niklaskorz | does rpy have pragmas? I'm not sure I want to go down that rabbithole | 23:30:04 |
| emily | ah, yeah that's a mystery :) | 23:33:54 |
| emily | the latter solution might be easiest for them | 23:34:01 |
| 16 Dec 2025 |
| Randy Eckenrode | When did SwiftPM get support for traits? | 03:11:38 |
 samasaur | very recently! 6.2 I think | 03:58:27 |
| niklaskorz | tailscale cli fails for {aarch64,x86_64}-darwin on both unstable and 25.11 due to test failures (something about a closed connection), they pass on 25.05, hm | 11:08:57 |
| niklaskorz | ok narrowed it down to https://github.com/NixOS/nixpkgs/pull/465025 | 11:09:42 |
| niklaskorz | they do pass locally on aarch64-darwin though, and in the PR apparently also did pass locally on x86_64-darwin | 11:10:25 |
 WeetHet | I got tired of running a separate nix in OrbStack. Is there an example of setting it up as a linux builder? | 11:12:53 |
| WeetHet | Do I just add it via nix.buildMachines? | 11:13:29 |
| niklaskorz | nix.linux-builder.enable = true; | 11:15:41 |
| niklaskorz | in nix-darwin | 11:15:43 |
| niklaskorz | oh you mean the nix in orbstack | 11:15:51 |
| niklaskorz | sorry | 11:15:52 |
| WeetHet | That uses qemu | 11:15:55 |
| WeetHet | I want to use orbstack | 11:16:03 |
| WeetHet | * I want to use orbstack (which uses Virtualisation.framework) | 11:16:14 |
| niklaskorz | there is a module that also uses Virtualisation framework fwiw | 11:16:24 |
| niklaskorz | but if you have a Linux VM running inside OrbStack, then it'd work like any remote builder, yeah | 11:16:36 |
