| 9 Mar 2025 |
 Andrew | so you're saying there should be a cache for llvm? | 16:21:24 |
| Andrew | I'm not sure if you build the build tools for different target, how would I then be able to use them to build the program for that target if those build tools are not for my host target. | 16:23:02 |
 emily | they are rebuilt for a different --target, but the same --host. | 16:23:18 |
| Andrew | Or does it compile so that I can run them from the host target to build the target-target? | 16:23:26 |
| emily | that is what pkgsCross.<system>.buildPackages means | 16:23:26 |
| emily | no, I'm saying it's probably a packaging infelicity | 16:23:46 |
| Andrew | uhhh, so there shouldn't be any cache for llvm? | 16:24:41 |
| Andrew | 4467 steps is soo much... | 16:25:10 |
| Andrew | home.packages = with pkgs; [
cargo
clippy
rustc
pkgsCross.wasi32.buildPackages.rustc
rustfmt
rust-analyzer-nightly
cargo-expand
pkg-config
];
| 16:47:03 |
| emily | btw at least some WASI stuff should be cached because Firefox uses it. | 16:48:33 |
| Andrew | I can't build llvm as it eats all of the memory at step 1321/4467 with a lot of llvm-tblgen processes. | 16:48:41 |
| emily | ok.p | 16:48:49 |
| emily | * ok. | 16:48:53 |
| Andrew | so... I guess I'm back to basics and gonna use rustup like the old times... | 16:49:29 |
 loudgolem | you can try swapspace to autogrow your swap | 16:50:33 |
| loudgolem | if you have fast ssd storage to spare | 16:51:21 |
| loudgolem | * only if you have fast ssd storage to spare | 16:51:24 |
| loudgolem | I have been using it for around a year (and I also maintain it in nixpkgs). | 16:51:35 |
| Andrew | idk about fast, but it is SSD | 16:56:27 |
| Andrew | Do I need to reboot or no? | 16:59:48 |
| loudgolem | systemctl status swapspace should be green | 17:01:02 |
| Andrew | Is services.swapspace.enable = true; enough? | 17:01:20 |
| loudgolem | yes | 17:01:51 |
| Andrew | ok, I'll try then | 17:02:00 |
| loudgolem | then run the build again, also watch swapon --show in another window to monitor your swap | 17:02:23 |
| loudgolem | * then run the build again, also watch swapon --show in another window to monitor your swap files | 17:02:27 |
| Andrew | It does eat a ton of memory very rapidly, in a matter of 20 seconds or so. Not sure if swapspace can keep up with that | 17:02:33 |
| Andrew | Yeah, I'm interested in that. | 17:02:53 |
 K900 | I'd start by not building on a tmfps | 17:03:09 |
| K900 | If you are building on a tmpfs | 17:03:13 |
