EndilWayfare

Ayyyy, got it to work. __TL;DR: Compiling on Windows == still broken for me. Cross-compiling from Linux works if 1) target/host overrides are set correctly and 2) you make sure...

Dammit, just kidding. That was my _system_ `cargo.exe`, not `./build/cargo.exe`. The new cross-compiled `cargo` hangs forever like the `./y.rs build --sysroot none` version...

> I have never actually tried to cross-compile cg_clif itself for windows. CI tests compiling cg_clif on windows using the mingw toolchain and it tests compiling programs using cg_clif for...

> Maybe removing > > https://github.com/bjorn3/rustc_codegen_cranelift/blob/d498e6d6971575714353f11aa4d3e63a9d2030b2/build_sysroot/Cargo.toml#L23 > > helps? Ahhhh, the `Cargo.toml` in "build_sysroot", ok. I messed around with the root one, but I missed that there was another. Well,...

While I'm at it, is there a reason that the `windows` CI target is disabled from uploading its artifacts? Later today, I might get a chance to try compiling on...

Ok, I decided to let `cargo.exe` sit there for a while and find out if it ever actually _does_ anything. It does. It allocates a lot of memory until it...

> Interestingly, it doesn't actually give me a backtrace oooooh, could that be a side-effect of `debug = true`?

It's also very probable that the windows CI build suffers from the same issue. The action only tests whether it _compiles_; `test.sh` isn't run, because windows. I tried running `test.sh`...

> I see what is going on. On Unix systems the directory containing the current executabe is not in `PATH`, so trying to spawn "cargo" will attempt to run the...

> Looks like the jit tests don't work. Could you try if disabling those tests will make the rest of the tests pass? It _looks_ like disabling jit tests and...