-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
missing libstdc++-6.dll in beta-x86_64-pc-windows-gnu (1.41.0-beta.1) #67408
Comments
Probably the culprit is here: https://github.com/rust-lang/rust/pull/67077/files#r359557571 |
As immediate workaround I suggest adding |
@mati865 Thanks! It works. |
triage: P-high, has PR, removing nomination. |
Sadly, that didn't work for me: "The procedure entry point _ZNSt13__future_base12_Result_baseC2Ev could not be located in the dynamic link library C:\Users\xxx\.rustup\toolchains\nightly-x86_64-pc-windows-gnu\bin\rustc_driver-3aaebb9b017b7498.dll." Just posting as an FYI, not expecting a solution. |
…lacrum Reenable static linking of libstdc++ on windows-gnu Fixes rust-lang#67408 Verified locally that `rustc_driver` is now statically linked to libstdc++.
…lacrum Reenable static linking of libstdc++ on windows-gnu Fixes rust-lang#67408 Verified locally that `rustc_driver` is now statically linked to libstdc++.
FWIW it was fixed in nightly but not yet in beta. |
Did this fix make it into stable? I'm getting that error in rustc 1.59.0 (9d1b210 2022-02-23). Cross-compiling from Linux: Trying to run under Wine 7.0. Wine error messages:
Please, statically link this stuff. (Trying to find the correct version of |
It was linked statically in the past, must be regression.
There are 2 versions shipped in Ubuntu: posix and win32. Posix is the correct one. |
Upon closer inspection you are not having problem running rustc but with artifacts built with rustc. |
Yes. I was using a deprecated package that pulled in some DLLs. Once I got rid of that package, the problem disappeared. |
@John-Nagle two questions: 1) how did you find the offending package, 2) which one was it? I'm getting the same thing on |
Looked through the build logs with "grep" for the package name. |
I couldn't find a specific dependency that caused the issue, but upgrading rust from |
I saw this failure in rayon CI: https://ci.appveyor.com/project/cuviper/rayon/builds/29634901/job/y7h1kc7w9wsusl8r
I'm on Linux, but I tried this build under Wine:
It seems @mati865's intention in #65911 was that this should be statically linked, but that was clobbered by #67077 in
src/bootstrap/compile.rs
at least.The same error occurs on
1.41.0-nightly (3ed3b8bb7 2019-12-17)
(via Wine again for me).The text was updated successfully, but these errors were encountered: