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.

Author steve.dower
Recipients docs@python, eryksun, jkloth, paul.moore, steve.dower, tim.golden, vstinner, zach.ware
Date 2017-05-15.19:45:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1494877551.36.0.16554798022.issue30350@psf.upfronthosting.co.za>
In-reply-to
Content
> That release is intended for building extension modules. Is it possible to configure it for building CPython

It's intended for extension modules, but should be usable for building CPython itself if someone wants to take the time to update the Python 2.7 build system to use it. (Also, there's nothing wrong with the 64-bit toolset in this installer - that was the Windows SDK version of the compilers.)

The main reason you can't use it is because our build system is MSBuild based and the compiler package does not register with MSBuild (it doesn't provide a Platform Toolset). It would be possible to write one that would work, though I don't know exactly how to do it - I believe ICC and clang both provide the required files though, so it may be relatively easy to add the toolset files into our source repo and make it work.

There are likely some other reasons that the build will fail, but those can likely be worked around within the source repository.
History
Date User Action Args
2017-05-15 19:45:51steve.dowersetrecipients: + steve.dower, paul.moore, vstinner, tim.golden, jkloth, docs@python, zach.ware, eryksun
2017-05-15 19:45:51steve.dowersetmessageid: <1494877551.36.0.16554798022.issue30350@psf.upfronthosting.co.za>
2017-05-15 19:45:51steve.dowerlinkissue30350 messages
2017-05-15 19:45:51steve.dowercreate