Philipp Oppermann

> The following skips the unexpected core-rebuilding and sysroot-wide lockfile. I.e. `cargo run` in one shell shouldn't block other use of `cargo *`. Nice! If using cargo-xbuild, I would configure...

Thanks for reporting! The reason that this doesn't properly work is that we do two cargo invocations behind the scenes. The first invocation is for building the sysroot crates (`core`,...

> I got the -Z option working by using `-Z build-std=core,alloc`. Sorry, I forgot about alloc.

Which version of cargo-xbuild are you using? There was an issue that might cause this in version 0.5.1, which should be fixed in version 0.5.2.

Ok, then it's something different. When does it fail? When linking the sysroot (i.e. `core`, `alloc` etc) or when linking your crate?

Could you do a `cargo clean` and then recompile it with the `--verbose` flag and post the output here? Cargo-xbuild should only execute a normal `cargo` command and set the...

Thanks! According to the [cargo documentation](https://doc.rust-lang.org/cargo/reference/config.html#configuration-keys), the linker argument should be passed as `-C linker=` to `rustc`, but it seems like this does not happen here. I have no idea...

Ok, then this is an issue with cargo itself. It seems like the `[target.arm-none-eabi]` block is applied, since the `target-cpu=cortex-a8` argument is in the verbose output, so this does not...

We just published a new Rust OSDev newsletter: [**This Month in Rust OSDev: April 2024**](https://rust-osdev.com/this-month/2024-04/). Happy reading!

We just released a new Rust OSDev newsletter: [**This Month in Rust OSDev: June 2024**](https://rust-osdev.com/this-month/2024-06/) (sorry for forgetting to comment here for the May 2024 issue)