You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As crates are placed within libdir shouldn't introduce filesearch::get_or_default_libdir based on rustc_driver*.so location instead of using filesearch::get_or_default_sysroot based on binary location?
The text was updated successfully, but these errors were encountered:
o01eg
changed the title
Rustc_driver cann't correctly find std crate if the linked binary launched not from /usr/bin
Rustc_metadata cann't correctly find std crate if the linked binary launched not from /usr/bin
Dec 29, 2018
Same as #57014 issue happened with crate search:
If I launch
/usr/bin/clippy-driver
without setting sysroot it get correct default/usr
If I launch
/tmp/rust-clippy/target/release/clippy-driver
built from sources I get incorrect sysroot:Currently clippy solves it with launching rustc from PATH: https://github.com/rust-lang/rust-clippy/blob/980bcd8c537aaa7b157aae4f05f8edca9905e331/src/driver.rs#L52
As crates are placed within libdir shouldn't introduce
filesearch::get_or_default_libdir
based on rustc_driver*.so location instead of usingfilesearch::get_or_default_sysroot
based on binary location?The text was updated successfully, but these errors were encountered: