| 10 Sep 2024 |
colemickens | /nix/store/giwwj37z3bv7zcd9np4h1475gv6v723x-h96maxv58-disko-images.drv
└───/nix/store/icdy400c78p77dmg953x9n0s9cd51x81-h96maxv58-disko-images.drv
└───/nix/store/mw0b87v5jir4lv9qk50h3dahqznqicmc-vm-run.drv
└───/nix/store/3sc1kz031fhjq0m6lk0dd96zb23c9jck-qemu-host-cpu-only-9.1.0.drv
└───/nix/store/wgyx5ghqdsy6zjr2f43bd1k53mbryiki-mesa-aarch64-unknown-linux-gnu-24.2.0.drv
└───/nix/store/wzab9w8ak2mafl1gxwi811lbc7pyjcgl-source.drv
| 05:00:57 |
colemickens | error: a 'x86_64-linux' with features {} is required to build '/nix/store/wzab9w8ak2mafl1gxwi811lbc7pyjcgl-source.drv', but I am a 'aarch64-linux' with features {benchmark, big-parallel, gccarch-armv8-a, kvm, nixos-test}
| 05:01:13 |
colemickens | odd, odd, odd. | 05:01:17 |
colemickens | "aarch64-unknown-linux-gnu" looks like cross-comp but idk why | 05:02:10 |
colemickens | I'm looking at how imageBuilderPkgs is defaulted/used and how host/buildPlatform are set for the system that includes this module and it seems like everything should be fine | 05:07:38 |
colemickens | the next step would be vmTools, but also :/ I'm starting to doubt ? | 05:07:59 |
colemickens | maybe this is vmTools use of buildPackages, and maybe I can just set customQemu and get around it | 05:14:34 |
colemickens | well no that doesn't make sense, build and host is aarch64-linux. what the heck then. | 05:14:52 |
colemickens | matthewcroughan: https://github.com/NixOS/nixpkgs/pull/325619 doesn't this kinda not work since ${qemu} is still used for making the empty disk image, etc? | 05:40:54 |
colemickens | I'm so confused. If I build qemu_kvm or buildPackages.qemu_kvm it works, but if I build diskoImageScript it acts like it's crosscompiling from x86_64-linux. I've checked nixpkgs host/buildPlatform. :/ | 05:43:10 |
colemickens | xargs cp :/ | 06:25:21 |