-
Notifications
You must be signed in to change notification settings - Fork 13.1k
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
--libdir
is not used by rustc
and rustpkg
#11671
Comments
Okay this is not as easily fixable as I thought. But there's a doable (and IMO clean) solution: Readd what I had in my first version of #11045:
Probably don't make CFG_LIBDIR_RELATIVE configurable, but still calculate it from CFG_LIBDIR. Then add linker flags to target.mk like it was here: 89f8bc2 Before I create a PR with these two changes, I would want to know if this would get merged. @alexcrichton what are your thoughts on this? |
@jhasse, @alexcrichton, what is the status of this? As in current state CFG_LIBDIR makes no sense: when it is set and rust is installed, it can not compile any create because of
and this error is because rustc looks in hardcoded relative path. Have I missed something or --libdir option is broken at the moment? |
The configure script has changed slightly since this was opened, and so have the state of things. This isn't really relevant to rustpkg (now cargo), but it's still relevant for rustc. The configure script supports the |
I've submitted a PR with fix, please, have a look. It changes behavior for case when libdir different from 'lib' is provided. It is not very common use case, but can be usefull (e.g. I'm planning to use it in rust package in Gentoo to allow different versions of rust to be installed simultaneously). |
Fixies #11671 This commit changes default relative libdir 'lib' to a relative libdir calculated using LIBDIR provided by --libdir configuration option. In case if no option was provided behavior does not change.
After configuring and installing rust using the
--libdir
switch,rustc
andrustpkg
don't search in that dir:When building:
and
The text was updated successfully, but these errors were encountered: