This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: Building fails on Windows
Type: Stage: resolved
Components: Windows Versions: Python 3.7
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: Nosy List: paul.moore, pitrou, steve.dower, tim.golden, vstinner, xgdomingo, zach.ware
Priority: normal Keywords:

Created on 2017-12-12 17:45 by pitrou, last changed 2022-04-11 14:58 by admin. This issue is now closed.

Messages (12)
msg308145 - (view) Author: Antoine Pitrou (pitrou) * (Python committer) Date: 2017-12-12 17:45
Sorry if this looks more like a support request.  There's probably something wrong in my setup (I do have Visual Studio 2015 installed, though).

I am trying to build on Windows using "Tools\buildbot\build.bat -p x64".  It worked a few months ago.  Now I get:

Build FAILED.

       "c:\t\cpython\PCbuild\pcbuild.proj" (Build target) (1) ->
       "c:\t\cpython\PCbuild\pythoncore.vcxproj" (Build target) (2) ->
       (Desktop_PlatformPrepareForBuild target) ->
         C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Platforms\x64\P
       latformToolsets\v140\Toolset.targets(36,5): error MSB8036: The Windows S
       DK version 10.0.16299.0 was not found. Install the required version of W
       indows SDK or change the SDK version in the project property pages or by
        right-clicking the solution and selecting "Retarget solution". [c:\t\cp
       ython\PCbuild\pythoncore.vcxproj]

    0 Warning(s)
    1 Error(s)
msg308150 - (view) Author: Steve Dower (steve.dower) * (Python committer) Date: 2017-12-12 20:21
I changed the default Windows SDK version at some point, because it was falling back to v8.1 and we really ought to use v10. It auto-detects all the v10 versions, so I'm guessing you haven't got any of them installed right now.

The dev guide just says to install VS 2017, which will include it. We should probably have manual install steps listed somewhere as well, though I'm hesitant to make the "getting started" steps too complex. And I've already switched 3.7 to use the v141 toolset, which is in VS 2017 but not VS 2015 (but it's binary compatible with the older v140, so shouldn't matter).

For VS 2015, you can get the Windows 10 SDK from https://developer.microsoft.com/windows/downloads/windows-10-sdk (only the headers and libraries option is required).
msg308160 - (view) Author: Antoine Pitrou (pitrou) * (Python committer) Date: 2017-12-12 22:11
Thank you.  Though now I get the following issue:

       "c:\t\cpython\PCbuild\pcbuild.proj" (Build target) (1) ->
       "c:\t\cpython\PCbuild\pythoncore.vcxproj" (Build target) (2) ->
       (ResourceCompile target) ->
         TRACKER : error TRK0005: Failed to locate: "rc.exe". The system cannot
        find the file specified. [c:\t\cpython\PCbuild\pythoncore.vcxproj]
msg308176 - (view) Author: Steve Dower (steve.dower) * (Python committer) Date: 2017-12-13 00:14
Strange, that should have been installed.

Do you see rc.exe anywhere in "C:\Program Files (x86)\Windows Kits\10"? If not, might need to repair the SDK you just installed. It shouldn't be a separate option from anything else in there.
msg308178 - (view) Author: Antoine Pitrou (pitrou) * (Python committer) Date: 2017-12-13 00:54
Le 13/12/2017 à 01:14, Steve Dower a écrit :
> 
> Strange, that should have been installed.
> 
> Do you see rc.exe anywhere in "C:\Program Files (x86)\Windows Kits\10"?

Yes, it's in "C:\Program Files (x86)\Windows Kits\10\bin\10.0.16299.0\x64"
msg308179 - (view) Author: Steve Dower (steve.dower) * (Python committer) Date: 2017-12-13 01:05
Is there one in x86 as well? Perhaps it isn't finding x64 tools properly (I've seen this once or twice in the past with VS 2015, but I think it was fixed at some point)
msg308180 - (view) Author: Antoine Pitrou (pitrou) * (Python committer) Date: 2017-12-13 01:07
Yes, both in x86 and x64. And `tools\buildbot\build.bat` fails regardless of whether I pass `-p x64` or not.
msg308185 - (view) Author: Steve Dower (steve.dower) * (Python committer) Date: 2017-12-13 02:06
It shouldn't be any different, but what about PCBuild/build.bat?
msg308196 - (view) Author: Antoine Pitrou (pitrou) * (Python committer) Date: 2017-12-13 10:51
> It shouldn't be any different, but what about PCBuild/build.bat?

Yes, same thing.
msg308208 - (view) Author: Steve Dower (steve.dower) * (Python committer) Date: 2017-12-13 16:26
Are you using a normal command prompt or the Visual Studio one? Totally clean environment should work fine these days, but I suspect there's an environment variable affecting something.

"set" to show everything that is set, remove any personal info and post or just email it to me if you'd like me to check.
msg308209 - (view) Author: Antoine Pitrou (pitrou) * (Python committer) Date: 2017-12-13 16:29
It's a normal command prompt.  Here is the output of "set":
https://gist.github.com/pitrou/2baf9950b0ab2f68b39b4973355b2e79
msg308230 - (view) Author: Antoine Pitrou (pitrou) * (Python committer) Date: 2017-12-13 19:06
Ok, I've decided to bite the bullet.  I uninstalled VS 2015 and installed VS 2017 Community Edition.  Things seem to work now.  Thanks for the help!
History
Date User Action Args
2022-04-11 14:58:55adminsetgithub: 76473
2017-12-13 19:06:46pitrousetstatus: open -> closed
resolution: fixed
messages: + msg308230

stage: resolved
2017-12-13 16:29:25pitrousetmessages: + msg308209
2017-12-13 16:26:34steve.dowersetmessages: + msg308208
2017-12-13 10:51:51pitrousetmessages: + msg308196
2017-12-13 03:59:40xgdomingosetnosy: + xgdomingo
2017-12-13 02:06:11steve.dowersetmessages: + msg308185
2017-12-13 01:08:00pitrousetmessages: + msg308180
2017-12-13 01:05:32steve.dowersetmessages: + msg308179
2017-12-13 00:54:09pitrousetmessages: + msg308178
2017-12-13 00:14:08steve.dowersetmessages: + msg308176
2017-12-12 22:34:32vstinnersetnosy: + vstinner
2017-12-12 22:11:11pitrousetmessages: + msg308160
2017-12-12 20:21:42steve.dowersetmessages: + msg308150
2017-12-12 17:45:37pitroucreate