| 17 Jan 2026 |
Randy Eckenrode | If cross just happens to work, yay. I doubt it will, though we’re closer than we are currently. | 18:50:26 |
emily | I was wondering whether we can avoid this "looking at its own location" by just putting that stuff in the SDK. | 18:51:47 |
emily | then the SDK is a build input, a la apple-sdk. the compiler could propagate the ones for the host and target platforms | 18:52:45 |
Randy Eckenrode | We would have to vend a special SDK on Darwin that adds the Swift libs the apple-sdk. | 19:30:39 |
Randy Eckenrode | Maybe we can do that, but it can be done in a follow up. | 19:30:56 |
emily | ah, it expects the other macOS SDK stuff mixed in with the Swift stuff? fun | 20:39:11 |
Randy Eckenrode | It maps SDKROOT to --sdk automatically. | 20:41:00 |
emily | gotcha | 20:43:05 |
Ihar Hrachyshka | compiler-rt build fix for x86_64-darwin is confirmed: https://github.com/NixOS/nixpkgs/pull/480889 | 20:43:09 |
| 18 Jan 2026 |
gigamonster256 | I'm having trouble getting an app to run on x86_64-darwin derivation here: https://github.com/gigamonster256/opencode/blob/48050d51580cc332979c589e2ed260984f240cd6/nix/opencode.nix
opencode> 34 | export function systemArchitectureSync() {
opencode> 35 | const {arch, platform, env} = process;
opencode> 36 |
opencode> 37 | // Detect Node.js x64 binary running under Rosetta 2 on a ARM64 Mac.
opencode> 38 | if (platform === 'darwin' && arch === 'x64') {
opencode> 39 | const stdout = childProcess.execFileSync('sysctl', ['-inq', 'sysctl.proc_translated'], {encoding: 'utf8'});
opencode> ^
opencode> error: Executable not found in $PATH: "sysctl"
opencode> path: "sysctl",
opencode> errno: -2,
opencode> syscall: "spawnSync sysctl",
opencode> spawnargs: [ "-inq", "sysctl.proc_translated" ],
opencode> signal: null,
opencode> status: undefined,
opencode> output: [
opencode> null, null, null
opencode> ],
any advice for making sure the sysctl command is found? some sort of wrapProgram? adding sysctl to buildInputs didnt seem to make a difference
| 00:15:08 |
Randy Eckenrode | Try adding it to nativeBuildInputs. | 00:16:39 |
gigamonster256 | no dice on that either iirc, I'll double check, the failure happens when running install checks and generating shell completions | 00:18:47 |
Randy Eckenrode | https://github.com/NixOS/nixpkgs/pull/477520#issuecomment-3764540038 | 00:45:49 |
Randy Eckenrode | While I wasn’t successful due to not having intentbuilderc, that’s promising. | 00:46:09 |
eveeifyeve | Randy I had a look at your WIP progress swift build mk2 branch and had a bit of skim over, It's looking good.
However I am still not too sure if the by-name thing follows RFC 140 after reading your code by-name/sw/swift/by-name/sw/<package> and the rfc.
| 11:05:21 |
eveeifyeve | * Hey Randy! I had a look at your WIP progress swift build mk2 branch and had a bit of skim over, It's looking good. However I am still not too sure if the by-name thing follows RFC 140 after reading your code by-name/sw/swift/by-name/sw/<package> and the rfc. | 11:05:41 |
Randy Eckenrode | I will probably be keeping it in development/swift/compilers when it lands but using the by-name stuff like Tcl does. | 11:33:17 |
Randy Eckenrode | For now, I’m going to continue with it like this because it preserves the old packages for reference. | 11:34:06 |
Randy Eckenrode | emily had talked about the possibility of everything being moved to by-name for 26.05, which would include package sets. I was trying to get out in front of that. If it’s not ready when Swift lands, it will be where it has to be to satisfy the checks. | 11:52:56 |
Sarah Clark | I'm running into a problem where fetchFromGitHub expects one hash on darwin and another on linux. The sources are not being pulled from the build cache but directly from github. https://github.com/NixOS/nixpkgs/pull/477051 The issue appears to be some docs artifacts that use mixed-case filenames. Help? | 18:35:16 |
samasaur | you could probably just use postFetch to wipe out the conflicting files on linux so that the hash matches | 18:38:56 |
samasaur | though I'm not sure whether the behavior of case-insensitive APFS is deterministic as to which files remain | 18:40:25 |
Sarah Clark | That's a new one to me. Thanks! | 18:42:46 |
samasaur | actually uhhh. do you need docs/ at all? if not you could just rm -rf docs/ in postFetch and then you're definitely fine, because all the case-sensitive files are in that folder | 18:42:56 |
Sarah Clark | I don't need docs, so rm -rf it is. | 18:45:52 |
samasaur | that should be rm -rf $out/docs, sorry | 18:45:59 |
samasaur | but yeah if you don't need docs that sounds easiest | 18:46:07 |
samasaur | I would ofc leave a comment explaining why you're doing so | 18:46:57 |
Sarah Clark | Did so :) | 18:58:03 |
Sarah Clark | Nuts, that wasn't it. | 18:59:04 |