-
Notifications
You must be signed in to change notification settings - Fork 13.5k
Expose target libdir information via print command #69608
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Conversation
(rust_highfive has picked a reviewer for you, use r? to override) |
With custom libdir it is required to have an access to library placement.
r? @ehuss |
For Gentoo with custom libdir it looks like:
|
@ehuss Yes, I've updated it. |
Thanks! Normally I would want a test, but I think it would be quite tricky to do it reliably. I'll also likely use this in Cargo, so it will get some coverage there. @bors r+ rollup |
📌 Commit dbd1514 has been approved by |
🌲 The tree is currently closed for pull requests below priority 1000, this pull request will be tested once the tree is reopened |
…=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
Rollup of 7 pull requests Successful merges: - #69120 (Don't give invalid suggestion on desugared span.) - #69326 (mir-interpret: add method to read wide strings from Memory) - #69608 (Expose target libdir information via print command) - #69734 (Change DIBuilderCreateEnumerator signature to match LLVM 9) - #69800 (Compile address sanitizer test with debuginfo) - #69807 (Cleanup E0391 explanation) - #69820 (clean up E0392 explanation) Failed merges: r? @ghost
With custom libdir it is required to have an access to library placement.
See RazrFalcon/cargo-bloat#51