| 17 Mar 2025 |
 Tristan Ross | The P550 is a good option but unstable | 21:40:25 |
| Tristan Ross | I've tried builds on one and everything segfaults | 21:40:38 |
 Alex | Performance is also a problem, because it takes a lot of compute to build every change in Nixpkgs (AFAIK Hydra is the only sane way of getting things into the official cache). | 21:41:31 |
| Tristan Ross | Yeah, I didn't even try evals on it lol | 21:42:44 |
| Alex | Evals aren't a problem at all, since they run entirely on the Hydra master server, which is (presumably) x86. | 21:43:25 |
| Tristan Ross | Building stuff kept on failing because my VisionFive2 has a DMA issue with the NIC driver so ssh kept on crashing along with the P550 segfaults | 21:43:27 |
| Tristan Ross | In reply to @alex:tunstall.xyz
Evals aren't a problem at all, since they run entirely on the Hydra master server, which is (presumably) x86. Well, I'm considering others doing local eval. | 21:43:46 |
| Tristan Ross | Like once it's built, you have to consume it | 21:44:00 |
| Tristan Ross | To consume it, you need the hash which you get via evals | 21:44:12 |
 flx | About the stability issue. What about cross compilation? | 21:44:12 |
| Tristan Ross | Cross is fine | 21:44:24 |
| Tristan Ross | You just need something like Ampere or Epyc to do it | 21:44:37 |
| Alex | Assuming that the package works in cross anyway.
Emulated is also fine, but there may still be a few bugs in QEMU's RISC-V implementation. Just a few months ago, someone found a build error only reproducible on emulated RISC-V. | 21:45:31 |
| flx | What that be a reasonable option for the NixOS project to do? | 21:46:40 |
| Alex | Cross is impractical as soon as you try customising anything too, since that won't be in cache.
(I don't see how you could do "cross pkgs, native modules/configs" for a NixOS build.) | 21:47:44 |
