Shane Murphy

> for the record, I think I was wrong in how qemu is used, I believe it's actually using the one in the container, I thought that wasn't the case....

> for the record, I think I was wrong in how qemu is used, I believe it's actually using the one in the container, I thought that wasn't the case....

> Im not totally sure how qemu is eventually used I'll investigate more, but maybe you're correct and I was assuming correctly I think it is the QEMU used by...

> It actually does seem like this is solved with newer qemu versions! > > update with > > ``` > docker run --privileged --pull always --rm tonistiigi/binfmt:qemu-v8.0.4 -uninstall amd64...

Also that didn't seem to solve it for me.

> > Also that didn't seem to solve it for me. > > I get absolutely zero `MADV_DONTNEED` warnings when running from a clean slate with `cargo clean` using 8.0.4,...

Spoke too soon, `aarch64-linux-gnu-gcc` segfaults when running the build for `openssl-sys`. At least the MADV warnings are gone 😅

> Some more usage, sometimes I still get the warnings, sometimes no, not sure whats differing For me to get it consistent I deleted any other versions of binfmt through...

> the issue upstream has been closed and [tonistiigi/binfmt#122](https://github.com/tonistiigi/binfmt/issues/122) has been opened instead > > @ShaneMurphy2 in [#1238 (comment)](https://github.com/cross-rs/cross/issues/1238#issuecomment-1783408588)_ what error code did you get? ``` --- stderr aarch64-linux-gnu-gcc: internal...

@tikue what do you think about adding in [trait-variant](https://docs.rs/trait-variant/latest/trait_variant/index.html)? It fixes this use case (I tested it in my fork), and is [officially suggested](https://blog.rust-lang.org/2023/12/21/async-fn-rpit-in-traits.html#async-fn-in-public-traits) by the Rust lang team. Only...