Crush with Raspberry Pi

[pixster]

[pixster]

PROBLEM: Crush got to 186 and failed with my Pi 3 b+

[liljencrantz]

172 what? Please elaborate. I will happily help you out with compiling it on a Pi, but you're not giving me a lot to go on here. :-)

Attaching build logs to this issue would be a good start.

[pixster]

When excuted-- cd crush; cargo build

Get's as far as 186 of 251 186/251

Error given-- error: board failed Hope this helps!

Ted

---

On Sunday, August 9, 2020, 4:56:25 PM PDT, Axel Liljencrantz <[email protected]> wrote:  

186 what? Please elaborate. I will happily help you out with compiling it on a Pi, but you're not giving me a lot to go on here. :-)

Attaching build logs to this issue would be a good start.

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub, or unsubscribe.

[pixster]

I hope this helps!?

414 | disk_inodes_used, | ^^^^^^^^^^^^^^^^ | | | expected u64, found u32 | help: you can convert an u32 to u64: disk_inodes_used: disk_inodes_used.into()

error: aborting due to 6 previous errors

For more information about this error, try rustc --explain E0308. error: could not compile psutil.

Caused by: process didn't exit successfully: rustc --crate-name psutil --edition=2018 /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/psutil-1.7.0/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi --crate-type lib --emit=dep-info,metadata,link -Cembed-bitcode=no -C debuginfo=2 -C metadata=20e12e5fc62f044e -C extra-filename=-20e12e5fc62f044e --out-dir /home/pi/crush/target/debug/deps -L dependency=/home/pi/crush/target/debug/deps --extern lazy_static=/home/pi/crush/target/debug/deps/liblazy_static-8cec29331eea44f4.rmeta --extern libc=/home/pi/crush/target/debug/deps/liblibc-d8940d57618349dc.rmeta --cap-lints allow (exit code: 1) warning: build failed, waiting for other jobs to finish... Building [==========================================> ] 207/251

[pixster]

I hope this helps!?

414 | disk_inodes_used, | ^^^^^^^^^^^^^^^^ | | | expected u64, found u32 | help: you can convert an u32 to u64: disk_inodes_used: disk_inodes_used.into()

error: aborting due to 6 previous errors

For more information about this error, try rustc --explain E0308. error: could not compile psutil.

Caused by: process didn't exit successfully: rustc --crate-name psutil --edition=2018 /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/psutil-1.7.0/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi --crate-type lib --emit=dep-info,metadata,link -Cembed-bitcode=no -C debuginfo=2 -C metadata=20e12e5fc62f044e -C extra-filename=-20e12e5fc62f044e --out-dir /home/pi/crush/target/debug/deps -L dependency=/home/pi/crush/target/debug/deps --extern lazy_static=/home/pi/crush/target/debug/deps/liblazy_static-8cec29331eea44f4.rmeta --extern libc=/home/pi/crush/target/debug/deps/liblibc-d8940d57618349dc.rmeta --cap-lints allow (exit code: 1) warning: build failed, waiting for other jobs to finish... Building [==========================================> ] 207/251

---

This was NO help!!! I guess all I can do is hope someone comes up with an answer for the Raspberry Pi.

[liljencrantz]

OK, that's a lot more useful. Thanks for the updates!

It seems like you're getting a compilation error while compiling one of the dependencies of Crush, not Crush itself.

Specifically, the library that is causing the problem is named psutil. I checked, and there is a new version of psutil available. I have bumped the version used by crush, please do a git pull and see if this fixes the problem. If yes, YAY. If no, I suggest you open an issue in that projects issue tracker, here: https://github.com/rust-psutil/rust-psutil

Also, if the version bump doesn't fix this issue and you want to try out Crush before the issue is fixed in psutil, do the following:

• Delete the dependency from the file Cargo.toml
• Delete the line that says mod proc; from src/lib/mod.rs.
• Delete the line that says proc::declare(root)?; from src/lib/mod.rs.

This will mean that the commands kill and ps, used to display and send signals to processes on your system, will no longer be available, but other than that, Crush should function correctly.