cargo-bloat fails to find std libraries, it expects them to live in /usr/lib/rustlib about cargo-bloat HOT 14 CLOSED

What rustc --print=sysroot outputs?

from cargo-bloat.

here's the output:

rustc --print=sysroot
/usr

from cargo-bloat.

Do you have rustlib at all?

from cargo-bloat.

Sure, I've got full rust toolchain available. It's actually the case that cargo build is executed before cargo bloat, and the error only appears when cargo build has finished it's compile. It's most likely a problem that rustlib resides in /usr/lib64, and the folder isn't scanned by cargo-bloat.

from cargo-bloat.

The problem is that I don't know where rustlib is. Currently, cargo-bloat uses the same algorithm as rustc.

Maybe your distro has a patched rust?

from cargo-bloat.

here's the file list: rust-files.gz

from cargo-bloat.

Looks like a bug of your distro. Library should be in

/usr/lib64/rustlib/x86_64-unknown-linux-gnu/lib

and not in

/usr/lib64/rust-1.39.0/rustlib/x86_64-unknown-linux-gnu/lib

from cargo-bloat.

I initially thought it was the fact that it resides in /usr/lib64, since all debian based distros don't distinguish lib and lib64, but it makes sense to me. Will test now.

from cargo-bloat.

this got triggered by a bug in gentoo, as you mentioned. This is now fixed, gentoo bug for reference: https://bugs.gentoo.org/703744

thanks for pointing me towards it! :)

from cargo-bloat.

Glad to hear, since I'm using Gentoo too. =) Only I'm installing Rust via rustup.

from cargo-bloat.

Currently, cargo-bloat uses the same algorithm as rustc.

rustc found out alternative libdir because it compiled with alternative CFG_LIBDIR_RELATIVE environment:

https://github.com/rust-lang/rust/blob/a916ac22b9f7f1f0f7aba0a41a789b3ecd765018/src/librustc_session/filesearch.rs#L159

from cargo-bloat.

Can I access it via CLI?

from cargo-bloat.

No yet, I'm think it better to expose it with --print=libdir or so.

from cargo-bloat.

@RazrFalcon I've opened PR: rust-lang/rust#69608

from cargo-bloat.