Nix Cross Compiling | 566 Members | |
| 124 Servers |
| Sender | Message | Time |
|---|---|---|
| 2 Dec 2025 | ||
| I wonder how much it'll suck to just add it by default | 16:08:43 | |
| could this work with python3Minimal? | 16:10:25 | |
| Let's add it by default later. I would like to make it available at all for now. And yeah, good point, it should use python3Minimal | 16:11:49 | |
| also not sure how fancy we want to go, but couldn't the hook be null in non-cross situations | 16:23:54 | |
| that way we wouldn't have to guard it on every use | 16:24:14 | |
| I think it would be better to go the route to always include it by default. even in non-cross scenarios. the check is very cheap. | 16:25:21 | |
| yeah, eventually | 21:44:33 | |
| but until then it would ease adoption | 21:44:42 | |
| 3 Dec 2025 | ||
| I'm not sure, because maybe someone wants to use it in a non-cross scenario, and then they cannot, because it is null. | 03:42:34 | |
| 19:29:39 | ||
| 4 Dec 2025 | ||
| 01:45:01 | ||
| 04:20:24 | ||
How could we prevent contributers from including setuptools-rust as a native build input and force the usage of the setuptoolsRustBuildHook instead?I've been seeing this multiple times already and it always breaks cross. | 06:07:26 | |
The checkBinaryArchHook unfortunately isn't gonna cut it because we don't cross build in CI the trigger the failure. | 06:08:07 | |
Or would it make sense to improve setuptools-rust, so it pulls in the hook automatically? | 06:11:35 | |
| add the hook as propagated build input on setuptools-rust ? | 07:11:40 | |
| I guess | 07:36:55 | |
| fixed: https://github.com/NixOS/nixpkgs/pull/467796 | 12:34:19 | |
| OOps wrong link. Here: https://github.com/NixOS/nixpkgs/pull/467817 | 12:34:45 | |
| When will we add a cross package set to hydra BTW? | 13:06:37 | |
| It is kind of tiring to fix the same stuff over and over again. Broken cross builds should be a blocker in CI. Too much dev power is wasted on this. | 13:09:30 | |
| We have some | 13:24:33 | |
| It can't block all the builds | 13:24:41 | |
| That would break very badly | 13:24:52 | |
| 14:10:37 | ||
| Hi there, I’m posting here (maybe wrong room, dunno) because I’m having an issue with compiling an aarch64-linux package from a darwin remote builder. To further explain, I've set up the darwin.linux-builder on an M4 Macbook with the goal of being able to build aarch64-linux packages as I don't have any real aarch64-linux machine lying around. After following the steps from the manual, I have an aarch64-linux builder VM running and have updated the Mac Nix conf with the following:
When I try to build the package, after a few seconds I get the following error: I looked around a bit (surely not enough) but the only resources I found were referring to systemd. Since MacOS is using launchd, this is not of any help to my issue, or so I think. It's unclear if the error is from the local host or the remote builder. Does anyone has an idea as to how to fix this? | 14:27:15 | |
Try ssh-ng://builder@linux-builder?store=daemon | 14:44:41 | |
Got not an absolute path: 'daemon'. Is this setting trying to set a different store location than /nix/store? | 14:52:56 | |
| Ugh | 14:53:40 | |
In reply to @k900:0upti.meNot store build remote-store | 14:54:11 | |