наб

Even with the undocumented `--log-level=off` the fallback `cargo install` (and the index update, &c.) isn't quieted like with `--quiet` for `cargo install`.

It took this long to be reported, and I have a workaround for this usecase, so, please, by all means, no rush, and thanks for GitBSLR in general!

This still occurs on Windows x86_64 due to a shitload of `expected u32, found u64` errors, is there any way of resolving this non-intrusively?

Non-intrusive from an end-user POV, I meant :P Lemme try to have at this...

This seems to make it compile for me: ``` diff diff --git a/src/ll.rs b/src/ll.rs index 1b34a3d..c469e71 100644 --- a/src/ll.rs +++ b/src/ll.rs @@ -16,9 +16,6 @@ use libc::{ c_char, c_int, c_short,...

Yeah, fair. [`cfg(version)`](https://doc.rust-lang.org/beta/unstable-book/language-features/cfg-version.html) is experimental, so I effectively inlined the `rustc_version` crate, and pick the old path before rustc 1.55

Norepro on bullseye with `cargo 1.54.0 (5ae8d74b3 2021-06-22)`, but I *can* reproduce this on `cargo 1.56.0 (4ed5d137b 2021-10-04)`. The test in question has a comment saying "// Go can parse...

Sure, you'll need to: * ifdef away most of `cpuid[_non]_windows.cpp` on `__x86_64`/`__x86_64__`/`__i386`/`__i386__` – possibly supplying a different set of functions relevant to ARM * same for `iware::cpu::vendor_id()` in `vendor_id.cpp` and...

The suitable solution is but two posts up: https://github.com/ThePhD/infoware/issues/49#issuecomment-850851005. You have relevant hardware: write a port; IIRC there's nothing Very Surprising that will bite you in the arse in this....

VMs both (a) are not part of the system and (b) would require IPC with VirtualBox (not feasible, obvious reasons), Hyper-V, and/or being root to have a sensible read on...