Skip to content
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

Closed
ehuss opened this issue Sep 26, 2019 · 3 comments
Closed

Investigate custom libdir setting #48

ehuss opened this issue Sep 26, 2019 · 3 comments
Labels
implementation Implementation exploration and tracking issues

Comments

@ehuss
Copy link
Contributor

ehuss commented Sep 26, 2019

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 in config.toml. See find_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.

@ehuss ehuss added the implementation Implementation exploration and tracking issues label Sep 26, 2019
@ehuss
Copy link
Contributor Author

ehuss commented Apr 7, 2020

Note: Switch to --print=target-libdir once 1.43 is stable: rust-lang/rust#69608

@Ericson2314
Copy link

Per #49 (comment) wasn't this stuff going away anyways?

@ehuss
Copy link
Contributor Author

ehuss commented Apr 7, 2020

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!

@ehuss ehuss closed this as completed Apr 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
implementation Implementation exploration and tracking issues
Projects
None yet
Development

No branches or pull requests

2 participants