-
-
Notifications
You must be signed in to change notification settings - Fork 30.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
Embedded installer for Python 3.7.7 missing vcruntime140.dll #84111
Comments
The Windows python-3.7.7-embed-amd64.zip installer (released Mar 11 2020) appears to be missing vcruntime140.dll. As a result, running the python.exe or pythonw.exe included in that installer fails with a system error notifying you of the missing DLL. The 3.7.6 embedded install included this file. |
It appears the 3.7.7RC1 embedded installer was also missing the file. |
Thanks for the heads-up, I'll take a look. |
AMD64 Windows10 3.8 build failed with "(...)\pyproject.props(221,5): error : vcruntime14*.dll not found (...)": |
Same error on AMD64 Windows10 3.x: |
Ah, both of those buildbots are running Build Tools. Apparently there's a different layout for those. Note that the devguide provides instructions that can't be followed with the Build Tools - you need VS Community (at least): https://devguide.python.org/setup/#windows Hopefully by tonight I'll have proper work access so I can figure out why Build Tools don't install everything. It may just be that a configuration option was missed, and so the buildbot owners will have to modify their install. |
Other examples of failures. AMD64 Windows8.1 Non-Debug 3.x:
AMD64 Windows10 3.7:
|
It seems like many buildbots are broken. Maybe the "buildbot" label should be tried on PRs changing the Windows build system. x86 Windows7 3.7: D:\cygwin\home\db3l\buildarea\3.7.bolen-windows7\build\PCbuild\pyproject.props(214,5): error : vcruntime14*.dll not found under D:\Program Files\Microsoft Visual Studio\2017\BuildTools\VC\ [D:\cygwin\home\db3l\buildarea\3.7.bolen-windows7\build\PCbuild\pythoncore.vcxproj] |
Added a PR to make the failure silent, up until we're building a release package. That way it'll only bother me, and I can make sure that I have the right VS install. |
Okay, I think I've got an approach that works even on the apparently misconfigured installs on the buildbots (and some user machines, if this is the same underlying issue as bpo-38597). I wasn't able to reproduce it though, so I have no idea why they don't have the right redist version property. Hopefully using the last-found directory under Redist continues to make sense into the future. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: