-
Notifications
You must be signed in to change notification settings - Fork 13.3k
rustpkg is not looking at target libraries #11243
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
Comments
Should it be looking at target libraries only? I tried that and it results in rustc rejecting the std crate:
|
Correct, this is what Your installation looks suspicious because rustc should favor looking at rlibs over dlls, and it looks like there were no rlibs found. Additionally, there was a recent version change (0.9-pre => 0.9), so that may be coming into play here (if the compiler is expecting one but finding another) |
Ahh ... nevermind! I should have ran |
Is there a workaround for this until the PR lands? |
Yes, copy the library over. On Windows:
|
I need some help fixing the failed tests. When running
That doesn't sound right. Why does it only run 2 tests? (IRC is crowded atm, if this is not the right place to ask this, please tell me) |
I think that there are far fewer rustpkg tests on windows because they mostly only run on unix right now. |
Ah thanks! Didn't know that. Time to boot up Linux ;) |
It appears that rustpkg is only looking at the host libraries, which are notably missing things like rlibs and libnative (for now).
Rustpkg should be looking at the target libraries which have all the necessary goodies in their folders.
The text was updated successfully, but these errors were encountered: