| 31 Jul 2025 |
 dramforever | has anyone else seen this? i'm still testing it out but i just kinda want to sanity check it | 18:27:58 |
| dramforever | * i am currently completely baffled by rustc bootstrap.toml custom target behavior. it seems that straight up expects [target.'/path/to/target-spec.json'] | 18:30:51 |
| dramforever | target.'/.../mips64el_loongson2f-unknown-linux-gnuabi64.json'.linker -> works
target.mips64el_loongson2f-unknown-linux-gnuabi64.linker -> no effect | 18:33:19 |
 emily | do we use the rustc wrapper when building with Cargo? | 19:33:37 |
| emily | this matches my exepctations fwiw | 19:33:47 |
| emily | * this matches my expectatiosn fwiw | 19:33:49 |
| emily | * this matches my expectations fwiw | 19:33:51 |
 Alyssa Ross | In reply to @emilazy:matrix.org
do we use the rustc wrapper when building with Cargo? Yes | 19:36:20 |
| emily | answer: yes | 19:36:27 |
| emily | sorry in advance Alyssa | 19:36:33 |
| dramforever | but cargo expects target.mips64el_loongson2f-unknown-linux-gnuabi64.linker | 19:37:43 |
| emily | rustc and Cargo diverge weirdly more than you'd expect | 19:38:28 |
| Alyssa Ross | That's why we have all those platform attrs! | 19:39:52 |
| dramforever | right, so my understanding is correct | 19:42:55 |
| dramforever | and it is further evidence that rustcTarget is just not a thing | 19:46:05 |
| emily | well, it does say rustc, not Cargo :) | 19:48:30 |
| dramforever | last time i talked about this with alyssa we had a very heated ... not really argument, more of a hair pulling session | 19:55:16 |
| dramforever | where basically i'm still convinced that there is no reason to ever use rustcTarget | 19:55:31 |
