| 13 Aug 2025 |
 dramforever | * error occurred in cc-rs: target `5qiqhay6jpxpba0byyalp1jmcl7k9g2n-mips64el\_mips3-unknown-linux-gnuabi64` had an unknown architecture | 00:52:28 |
 emily | starting to think the Rust ecosystem has some problems | 00:53:26 |
| dramforever | * error occurred in cc-rs: target `5qiqhay6jpxpba0byyalp1jmcl7k9g2n-mips64el_mips3-unknown-linux-gnuabi64` had an unknown architecture | 00:55:36 |
| dramforever | cc-rs has problems, yes | 00:55:49 |
| dramforever | but also we shouldn't be doing this | 00:55:58 |
| emily | the hash thing? | 00:57:20 |
| dramforever | yeah | 00:57:24 |
| dramforever | hmm | 00:57:31 |
| emily | it seems worse to have names things can parse and make wrong conclusions about | 00:57:33 |
| dramforever | changing *Platform.rust causes rebuilds in gcc | 00:57:44 |
| 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 |
 Alyssa Ross | I thought it was for typing/validation | 11:46:23 |
| Alyssa Ross | I remember being a bit annoyed about it when it happened | 11:46:31 |
| Toma | interesting...
cmakeFlags was added to stdenv 7 years ago in https://github.com/hercules-ci/nixpkgs/commit/b3041b44552f50109760e7fa41a16636e4b4d5c0
and 3 years ago, some type-checking logic was added to it: https://github.com/hercules-ci/nixpkgs/commit/3173c3b6b61cd06620bda26ac8f0b674866d6101
in any case, I don't want to pollute this room anymore with cursed non-rust stuff, rust has enough cursed stuff itself. | 12:13:42 |
| Toma | * interesting...
cmakeFlags was added to stdenv 7 years ago in https://github.com/NixOS/nixpkgs/commit/b3041b44552f50109760e7fa41a16636e4b4d5c0
and 3 years ago, some type-checking logic was added to it: https://github.com/NixOS/nixpkgs/commit/3173c3b6b61cd06620bda26ac8f0b674866d6101
in any case, I don't want to pollute this room anymore with cursed non-rust stuff, rust has enough cursed stuff itself. | 12:31:08 |
| dramforever | mesonFlags is absolutely rust-relevant | 12:49:21 |
