-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cargo-bloat fails to find std libraries, it expects them to live in /usr/lib/rustlib #51
Comments
What |
here's the output:
|
Do you have |
Sure, I've got full rust toolchain available. It's actually the case that |
The problem is that I don't know where Maybe your distro has a patched rust? |
here's the file list: rust-files.gz |
Looks like a bug of your distro. Library should be in
and not in
|
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. |
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! :) |
Glad to hear, since I'm using Gentoo too. =) Only I'm installing Rust via rustup. |
|
Can I access it via CLI? |
No yet, I'm think it better to expose it with --print=libdir or so. |
@RazrFalcon I've opened PR: rust-lang/rust#69608 |
…=ehuss Expose target libdir information via print command With custom libdir it is required to have an access to library placement. See RazrFalcon/cargo-bloat#51
…=ehuss Expose target libdir information via print command With custom libdir it is required to have an access to library placement. See RazrFalcon/cargo-bloat#51
how to reproduce, with the example of a fresh git checkout:
this is on a x86_64 machine, hence there's /usr/lib64/${RUSTVERSION}/ where rustlib resides. Not sure wether that is excentric behavior from my distro? :-)
The text was updated successfully, but these errors were encountered: