| 13 Aug 2025 |
 dramforever | i wonder why | 00:58:43 |
| dramforever | aand i have successfully bonked | 01:30:43 |
| dramforever | chat is this a normal *System.rust
rust = {
platform = builtins.fromJSON (builtins.readFile "${./rust}/mips64el_mips3-unknown-linux-gnuabi64.json");
rustcTargetSpec = "${./rust}/mips64el_mips3-unknown-linux-gnuabi64.json";
# cargoShortTarget = "mips64el_mips3-unknown-linux-gnuabi64";
rustcTarget = "mips64el_mips3-unknown-linux-gnuabi64";
};
| 02:25:54 |
 emily | is the thing actually mips64el_mips3 | 03:55:31 |
| emily | I hate that | 03:55:36 |
| dramforever | that's not a real cpu name | 04:00:44 |
| dramforever | but yes i need mips3 | 04:00:48 |
| dramforever | rust's default mips64el is mips64r2 | 04:01:02 |
| dramforever | * but yes i need -march=mips3 | 04:01:18 |
| dramforever | why the hell does everything have mesonFlags | 05:17:22 |
| dramforever | why the hell is there cmakeFlags and mesonFlags in pkgs/stdenv/generic/make-derivation.nix | 05:18:03 |
| dramforever | i can't fix this, i'll leave this be | 06:08:45 |
 Toma | In reply to @dramforever:matrix.org
why the hell is there cmakeFlags and mesonFlags in pkgs/stdenv/generic/make-derivation.nix I was very surprised too when I first encountered it. | 11:36:27 |
| Toma | I'm guessing it is there so that splicing/cross doesn't make us use targetPackages or other hacky things (because cmake goes into nativeBuildInputs, shifting the offset)
just a guess, though | 11:44:01 |
| Toma | * I'm guessing it is there so that splicing/cross doesn't make us use targetPackages or other hacky things when setting up the cmake vars (because cmake goes into nativeBuildInputs, shifting the offset)
just a guess, though | 11:44:30 |
