[issue34575] Python 3.6 compilation fails on AppVeyor: libeay.lib was created with an older compiler

STINNER Victor added the comment: It seems like the bug has been fixed. Thanks Zachary Ware for the fix, and thanks everybody for helping to fix this cache issue ;-) -- resolution: -> fixed stage: patch review -> resolved status: open -> closed __

[issue34575] Python 3.6 compilation fails on AppVeyor: libeay.lib was created with an older compiler

Zachary Ware added the comment: New changeset 635461fca5e90c6e091f1e5b46adafc0d28bf0e2 by Zachary Ware in branch '3.6': [3.6] bpo-34575: Build with only VS2015 on AppVeyor (GH-9066) https://github.com/python/cpython/commit/635461fca5e90c6e091f1e5b46adafc0d28bf0e2 -- ___

[issue34575] Python 3.6 compilation fails on AppVeyor: libeay.lib was created with an older compiler

STINNER Victor added the comment: Discussion on python-dev: https://mail.python.org/pipermail/python-dev/2018-September/155075.html -- ___ Python tracker ___ _

[issue34575] Python 3.6 compilation fails on AppVeyor: libeay.lib was created with an older compiler

Change by Zachary Ware : -- keywords: +patch pull_requests: +8530 stage: -> patch review ___ Python tracker ___ ___ Python-bugs-lis

[issue34575] Python 3.6 compilation fails on AppVeyor: libeay.lib was created with an older compiler

Paul Moore added the comment: One thought - appveyor.yml says that the cache of externals depends on PCBuild. Could it be that appveyor is caching PCBuild to verify whether it's changed (and hence whether to use the cached externals)? I know that sounds bizarre, but I'm not entirely sure why

[issue34575] Python 3.6 compilation fails on AppVeyor: libeay.lib was created with an older compiler

Karthikeyan Singaravelan added the comment: Ah ok, I thought disabling the cache with APPVEYOR_CACHE_SKIP_RESTORE as true will trigger a successful build and in the end it will store the new set of artifacts from the recent compiler to the cache and then we can toggle the environment variabl

[issue34575] Python 3.6 compilation fails on AppVeyor: libeay.lib was created with an older compiler

STINNER Victor added the comment: > APPVEYOR_CACHE_SKIP_RESTORE - set to true to disable cache restore > APPVEYOR_CACHE_SKIP_SAVE - set to true to disable cache update I see these as well, but it would only be a temporary solution and may make build much slower, whereas AppVeyor is already a

[issue34575] Python 3.6 compilation fails on AppVeyor: libeay.lib was created with an older compiler

Karthikeyan Singaravelan added the comment: One another way will be to set environment variable to skip the cache restore and trigger a build to see if cache is the actual problem. I don't know how configurable environment variables are from the UI to trigger a specific build with the set of

[issue34575] Python 3.6 compilation fails on AppVeyor: libeay.lib was created with an older compiler

Karthikeyan Singaravelan added the comment: Another way will be to invalidate the cache by manually updating cleanup-cache.txt in the end. But this requires a commit that has to be reverted later to enable caching and I don't think it's worthy to pollute git history for this. https://help.a

[issue34575] Python 3.6 compilation fails on AppVeyor: libeay.lib was created with an older compiler

STINNER Victor added the comment: Ah! If I user my personal account which has a different token, I'm able to list my roles using the REST API. So it seems that I lack some permissions on the "python" account of AppVeyor. Who owns this account? -- ___

[issue34575] Python 3.6 compilation fails on AppVeyor: libeay.lib was created with an older compiler

Paul Moore added the comment: I don't see an appveyor.yml file in the CPython repository. How are the appveyor builds configured? I was going to take a look, but need to see the config :-( On Wed, 5 Sep 2018 at 10:32, STINNER Victor wrote: > > > STINNER Victor added the comment: > > REST API

[issue34575] Python 3.6 compilation fails on AppVeyor: libeay.lib was created with an older compiler

STINNER Victor added the comment: REST API for the AppVeyor build cache: https://www.appveyor.com/docs/build-cache/#rest-api Authentication of the REST API: https://www.appveyor.com/docs/api/#authentication I tried: $ curl -H "Authorization: Bearer " -X "DELETE" https://ci.appveyor.com/api/

[issue34575] Python 3.6 compilation fails on AppVeyor: libeay.lib was created with an older compiler

Karthikeyan Singaravelan added the comment: If it's due to cache then there is a REST API to clear the cache manually and someone with access to Appveyor credentials can give it a try to clear the cache and see if it's fixed. Ref : https://github.com/appveyor/ci/issues/985 Log in and execut

[issue34575] Python 3.6 compilation fails on AppVeyor: libeay.lib was created with an older compiler

Steve Dower added the comment: Works on VSTS build. I suspect AppVeyor is caching files between builds, but I'm not familiar enough with the configuration to fix that. -- ___ Python tracker

[issue34575] Python 3.6 compilation fails on AppVeyor: libeay.lib was created with an older compiler

New submission from STINNER Victor : Example on my PR: https://github.com/python/cpython/pull/9057 https://ci.appveyor.com/project/python/cpython/build/3.6build21480/job/lge7r4qknx0t0tlv LINK : fatal error C1047: The object or library file 'C:\projects\cpython\PCBuild\win32\libeay.lib' was cr