-
Notifications
You must be signed in to change notification settings - Fork 8
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
Investigate custom libdir setting #48
Labels
implementation
Implementation exploration and tracking issues
Comments
Note: Switch to |
Per #49 (comment) wasn't this stuff going away anyways? |
Oh, hmm. Yea, it was removed in rust-lang/cargo#7699. Cargo still uses the libdir for some other dylib nonsense, but it is not related to build-std. Closing since this seems resolved, thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Cargo assumes a specific sysroot layout (primarily here). However, rustc may be built in such a way that the lib directory name is different from the default of "lib". This is via
install.libdir
inconfig.toml
. Seefind_libdir
.I was unable to find any targets built by rust-lang that set this parameter. Rumor is that some linux distributions may set it (to things like "lib32" or "lib64"), but I cannot find any active linux distribution that does that.
This needs investigation to understand the impact, and what needs to be done. AFAIK,
rustc
cannot be queried for this path, so there is no way to discover how it is compiled.The text was updated successfully, but these errors were encountered: