-
Notifications
You must be signed in to change notification settings - Fork 6.4k
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
bzip2:x64-windows-static build failure #17517
Comments
Have full debug log (posted as own comment below) |
2021-04-26T12:18:54.7786584Z ##[section]Starting: Install/Update vcpkg libs |
@unusual-aspect, could you run the powershell or command as Administrator, if so, do you set '-DVCPKG_CONCURRENCY=5' personaly? if so, could you unset it and see if it still persist? I tried it in my 2 test machines, I could not repro this issue locally. |
@PhoebeHui - this will work on any local box, but is not working on Azure DevOps pipeline on vmImage: 'windows-latest'. |
I think i found a problem, but not sure how to test/configure. On my local machine VCPKG_PLATFORM_TOOLSET is v141, on Azure Cloud is v142, they are binary compatible, but they may not work on compile mode. Not sure, also how to enforce v141 version on pipeline build. I try to test/re-create same way as: https://github.com/CE-Programming/CEmu/blob/master/appveyor.yml |
Changed image on Azure pipeline to: vmImage: 'vs2017-win2016' - and working fine! I think about two solutions:
|
@unusual-aspect, you can set VCPKG_PLATFORM_TOOLSET in triplet files. For the second solution, I would not recommand. For me, it looks like a permission issue, rather a vs toolset issue, so both v142 and v141 should work here, it may relate to the vm image itself. |
@unusual-aspect, does this still be a problem for you? |
@unusual-aspect, please reopen this issue if it still be a problem for you. |
Host Environment
To Reproduce
Steps to reproduce the behavior:
git clone vcpkg
bootstrap-vcpkg.bat -disableMetrics
vcpkg.exe install bzip2:x64-windows-static
Failure logs
The text was updated successfully, but these errors were encountered: