[issue46217] 3.11 build failure on Win10: new _freeze_module changes?

Terry J. Reedy added the comment: Thank you. Compiles without even any warnings. Tests also all pass. -- ___ Python tracker ___ _

[issue46217] 3.11 build failure on Win10: new _freeze_module changes?

Change by Steve Dower : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___ P

[issue46217] 3.11 build failure on Win10: new _freeze_module changes?

Steve Dower added the comment: New changeset d81182b8ec3b1593daf241d44757a9fa68fd14cc by Steve Dower in branch 'main': bpo-46217: Revert use of Windows constant that is newer than what we support (GH-30473) https://github.com/python/cpython/commit/d81182b8ec3b1593daf241d44757a9fa68fd14cc -

[issue46217] 3.11 build failure on Win10: new _freeze_module changes?

Change by Steve Dower : -- keywords: +patch pull_requests: +28676 stage: backport needed -> patch review pull_request: https://github.com/python/cpython/pull/30473 ___ Python tracker _

[issue46217] 3.11 build failure on Win10: new _freeze_module changes?

Change by Terry J. Reedy : -- nosy: +pablogsal ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue46217] 3.11 build failure on Win10: new _freeze_module changes?

Eryk Sun added the comment: Terry, it's just a simple bug that slipped by. The PATHCCH_OPTIONS enum in the SDK header "PathCch.h" unconditionally defines all of the options. So there's no compiler error when building with a newer version of the SDK, even though we define _WIN32_WINNT to 0x60

[issue46217] 3.11 build failure on Win10: new _freeze_module changes?

Steve Dower added the comment: Only a newer WinSDK, which is not in any way a significant change to the resulting build and so isn't part of the "spec" as it were. But we'll remove the use of this flag once someone has the time to make a PR. (Remember to add the RM when you declare something

[issue46217] 3.11 build failure on Win10: new _freeze_module changes?

Terry J. Reedy added the comment: Let me be clearer. This bug prevents me from building main (3.11) to test anything with a proper up-to-date 3.11 binary. So to me this is highest priority. Is this just my machine or every Windows system? How are CI and buildbots rebuilding and running?

[issue46217] 3.11 build failure on Win10: new _freeze_module changes?

Eryk Sun added the comment: With just PATHCCH_ALLOW_LONG_PATHS, PathCchCombineEx() returns a long path as a normal path (i.e. not a \\?\ extended path) if long-path support is enabled for the current process. Otherwise, if long-path support isn't enabled or available, as is always the case i

[issue46217] 3.11 build failure on Win10: new _freeze_module changes?

Steve Dower added the comment: Good catch. We still support 8.1 for this release, so that flag will have to be taken out (and hopefully people won't be impacted by long path names here). -- ___ Python tracker _

[issue46217] 3.11 build failure on Win10: new _freeze_module changes?

Change by Dong-hee Na : -- nosy: +corona10 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pytho

[issue46217] 3.11 build failure on Win10: new _freeze_module changes?

neonene added the comment: The flag is not for Win8.1 and available starting in Win10 1703 with v10.0.15021 SDK. -- nosy: +neonene ___ Python tracker ___

[issue46217] 3.11 build failure on Win10: new _freeze_module changes?

Change by Terry J. Reedy : -- components: +Windows nosy: +paul.moore, steve.dower, tim.golden, zach.ware ___ Python tracker ___ ___

[issue46217] 3.11 build failure on Win10: new _freeze_module changes?

New submission from Terry J. Reedy : Installed 3.11.0a3 was built Dec 8 2021, 22:56:33. My corresponding repository build is a bit older than that. Rebuilding now I get fileutils.c ..\Python\fileutils.c(2132): error C2065: 'PATHCCH_FORCE_ENABLE_LONG_NAME_PROCE SS': undeclared identifier [f