| 1 Jul 2025 |
 dramforever | oh god | 15:39:48 |
 Alyssa Ross | Okay rust-hypervisor-firmware may not actually be broken. Apparently it's expected to build it without cross compiling explicitly, and you have to allow unsupported systems: https://github.com/NixOS/nixpkgs/pull/378694#issuecomment-2637739053 | 15:40:21 |
 emily | …I'd call that broken | 15:41:01 |
| Alyssa Ross | It's evidently in use, or at least cared about | 15:41:21 |
| dramforever | no i think that's just the meta.platforms being wrong | 15:41:53 |
| dramforever | oh wait no it's doing cross compile in secret | 15:42:07 |
| Alyssa Ross | yeah | 15:42:11 |
| Alyssa Ross | it's horrible | 15:42:12 |
| dramforever | but then that new rustPlatform should pick up the right platform | 15:42:22 |
| dramforever | anyway the unsupported platform thing is just a meta issue i think | 15:42:59 |
| emily | I have a ridiculous idea for the target spec things | 15:43:50 |
| emily | what if we make a directory and put nixpkgs-{build,host,target}-platform.json symlinks to the rustcTargetSpec in there | 15:44:26 |
| emily | then the derivation hashes don't get included in the names | 15:44:51 |
| dramforever | you mean like in prePhases? | 15:45:21 |
| dramforever | wait how do we find the file then | 15:50:03 |
| dramforever | does rustc have a TARGET_SPEC_DIR or something | 15:50:47 |
| dramforever | you know what, nevermind, i'm not actually blocked on r-h-f | 15:59:26 |
| dramforever | i don't have the string with context problem if i use rust.framepointers | 15:59:48 |
| dramforever | * i don't have the string with context problem if i use rust.frame-pointers | 16:02:24 |
