-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
rustbuild: Restore Config.libdir_relative #48362
Conversation
This re-introduces a `Config.libdir_relative` field, now derived from `libdir` and made relative to `prefix` if necessary. This fixes a regression from rust-lang#46592 when `--libdir` is given an absolute path. `Builder::sysroot_libdir` should always use a relative path so its callers don't clobber system locations, and `librustc` also asserts that `CFG_LIBDIR_RELATIVE` is really relative.
(rust_highfive has picked a reviewer for you, use r? to override) |
Hm, so I think this is fine in general, but could we make |
OK, it's now a method. Can we also nominate this for beta? |
@bors r+ I've accepted for beta backport. |
📌 Commit 8174c0d has been approved by |
Thanks! |
…ulacrum rustbuild: Restore Config.libdir_relative This re-introduces a `Config.libdir_relative` field, now derived from `libdir` and made relative to `prefix` if necessary. This fixes a regression from rust-lang#46592 when `--libdir` is given an absolute path. `Builder::sysroot_libdir` should always use a relative path so its callers don't clobber system locations, and `librustc` also asserts that `CFG_LIBDIR_RELATIVE` is really relative.
This re-introduces a
Config.libdir_relative
field, now derived fromlibdir
and made relative toprefix
if necessary.This fixes a regression from #46592 when
--libdir
is given an absolutepath.
Builder::sysroot_libdir
should always use a relative path soits callers don't clobber system locations, and
librustc
also assertsthat
CFG_LIBDIR_RELATIVE
is really relative.