text:
No keyboard input in Windows Terminal running with "runas /netonly user:" flags from elevated shell

Windows Terminal version (or Windows build number)
10.0.19042.0, 1.7.1091.0
Other Software
Guest OS Windows 10 20H2 (10.0.19042.0) inside Oracle VM VirtualBox (6.1.20 r143896). Not in domain
Host Ubuntu 20.04
Windows Terminal 1.7.1091.0
Steps to reproduce

Run cmd (or Windows Terminal) as administrator
Run "runas /netonly /user:%username% wt.exe"
*wt.exe linking to Windows Terminal executable
Windows Terminal windows opens, but keyboard input is not working

Expected Behavior
Expecting keyboard to work in Windows Terminal's command promt.
When running not elevated cmd (or Windows Terminal) and launching Windows Terminal via "runas..." (from non elevated shell) everything works fine.
Actual Behavior
No keyboard input in Windows Terminal launched from elevated shell via "runas...". Mouse selecting and clicking (copy/paste) works fine.

Huh, this is weird. This is kinda like #8045, #4448, but different in that input works fine while unelevated. @ebadger, do you have any ideas as to what might be going on here?

@fmj9 Curious to know if input into notepad works if you launch it in the repo way.
for example:
Run cmd (or Windows Terminal) as administrator
Run "runas /netonly /user:%username% notepad.exe"
Does typing into notepad work?

Yes, when I launch notepad via runas typing into notepad works fine.
Same when I launch cmd or powershell. The problem only occurs when I'm starting Windows Terminal this way

I also experience this issue. I can paste by right-clicking, but no keyboard input works except for the window chrome (e.g. CTRL+SPACE). If I open the settings panel, then no keyboard input works there either.
Version: 1.13.11431.0

can you check your tasklist to see if ctfmon.exe is running?

Yes, ctfmon.exe is running.

@ebadger any ideas? Could this be an issue with multiple user accounts?

I'm unsure if this is related, but I suspect it is...
On my work laptop image we use BeyondTrust/PowerBroker to elevate processes. When I use BeyondTrust to elevate wt.exe, no keyboard input is received, but only to that window. And yes, ctfmon.exe is running.
Global shortcuts like Alt+Space do work, and you can close the Alt+Space popup with the ESC key too.  (Obviously since this all runs from dwm, I'm guessing.) Absolutely nothing else works, including tab, function keys, etc. The behavior is not as if there's a secondary key being held down like Alt (e.g. pressing Tab does not result in an Alt+Tab popup).
There are no messages in the Application or System events in Event Viewer pertaining to any of this that I can find. I also was not able to quickly (in under 10 minutes) find a way to enable additional logging for Windows Terminal itself, so I cannot provide logs.
Running cmd.exe using BeyondTrust allows keyboard input, but then when I execute the Windows Terminal wt.exe executable from that elevated cmd.exe window, the input again does not work for the WT window. (cmd.exe [elevated] -> wt.exe [elevated] -> no keyboard input)
Now for the interesting part... when I run wt.exe from an ELEVATED cmd.exe using:
runas /trustlevel:0x20000
The WT input still does not work, despite the WT instance being run with non-elevated permissions (tab in WT does not show "Administrator: " in front of it). (cmd.exe [elevated] -> Run as [de-escalated] wt.exe -> no keyboard input)
It's like it's some kind of process isolation issue almost given how utterly stubborn it is being to any kind of user input in that window. We do also use the following McAfee products:
Data Exchange Layer
Drive Encryption Agent
DLP Endpoint
Application Control
Endpoint Security
As well as FireEye endpoint security.

MSFT:43611188 for internal tracking purposes, we'll see what the input folks have to say

authors: Phorin carlos-zamora ebadger fmj9 mitchellrj zadjii-msft


text:
Apply dark window borders to NonClientIslandWindow using ThemeHelpers

This solution was vetted by the DWM team.
Fixes #3425.

@msftbot merge this in 2 minutes

I made sure that this put the dll file in the x64 appx layout, but I'll be watching our prod builds to make sure.

source: gharchive/pull-request

authors: DHowett-MSFT zadjii-msft

repo: microsoft/terminal

license: MIT

license_type: permissive

license_source: github-api


text:
[http-spec] add none visibility test

all emitter's test should not be affected by this change since the added property should not exist in any payload.

All changed packages have been documented.

:white_check_mark: @typespec/http-specs

Show changes
@typespec/http-specs - feature ✏

add none visibility test

You can try these changes here

🛝 Playground
🌐 Website
📚 Next docs

authors: azure-sdk tadelesh

repo: microsoft/typespec


text:
[libpopt] libpopt servers appear to be gone

Host Environment

OS: Any
Compiler: Any

To Reproduce
Steps to reproduce the behavior:
./vcpkg install libpopt
Failure logs
PS D:\vcpkg-master> .\vcpkg.exe install libpopt
Computing installation plan...
The following packages will be built and installed:
    libpopt[core]:x86-windows
Starting package 1/1: libpopt:x86-windows
Building package libpopt[core]:x86-windows...
-- Downloading http://rpm5.org/files/popt/popt-1.16.tar.gz...
CMake Error at scripts/cmake/vcpkg_download_distfile.cmake:99 (message):

  File does not have expected hash:

          File path: [ F:/downloads/temp/popt-1.16.tar.gz ]
      Expected hash: [ bae2dd4e5d682ef023fdc77ae60c4aad01a3a576d45af9d78d22490c11e410e60edda37ede171920746d4ae0d5de3c060d15cecfd41ba75b727a811be828d694 ]
        Actual hash: [ e9c99dcefad469c75cd4eb80eacff55f5d88fb6500309bc2a520d1d03b8aff2b00406de4fda2a47cae71847aa54ad214a1c5c5690a940badf723777d32a488a3 ]

  The file may have been corrupted in transit.  This can be caused by
  proxies.  If you use a proxy, please set the HTTPS_PROXY and HTTP_PROXY
  environment variables to
  "https://user:password@your-proxy-ip-address:port/".

Call Stack (most recent call first):
  scripts/cmake/vcpkg_download_distfile.cmake:182 (test_hash)
  ports/libpopt/portfile.cmake:6 (vcpkg_download_distfile)
  scripts/ports.cmake:90 (include)

Error: Building package libpopt:x86-windows failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with `.\vcpkg update`, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
  Package: libpopt:x86-windows
  Vcpkg version: 2020.02.04-nohash

Additionally, attach any relevant sections from the log files above.

Additional context
There are 2 servers for this package listed in the port file. One server, rpm5.org, appears to be completely gone. The other server, ftp.openbsd.org, appears to no longer host any version of this package.
We may want to consider outright delisting the package.

The primary is definitely mia.
Maybe the alternate was temporarily offline:
https://ftp.openbsd.org/pub/OpenBSD/distfiles/

https://ftp.openbsd.org/pub/OpenBSD/distfiles/popt-1.16.tar.gz seems to worked, it even had the correct hash checksum...
bae2dd4e5d682ef023fdc77ae60c4aad01a3a576d45af9d78d22490c11e410e60edda37ede171920746d4ae0d5de3c060d15cecfd41ba75b727a811be828d694  popt-1.16.tar.gz

Due to port openscap builds depend on libpopt, I think we should remove the invalid URL "http://rpm5.org/files/popt/popt-${LIBPOPT_VERSION}.tar.gz". libpopt can use https://ftp.openbsd.org/pub/OpenBSD/distfiles/popt-${LIBPOPT_VERSION}.tar.gz to install successfully.

source: gharchive/issue

authors: BillyONeal LilyWangL timautry

repo: microsoft/vcpkg


text:
openssl build failure

Host Environment

OS: Win10
Compiler: revision

To Reproduce
Steps to reproduce the behavior:
.\vcpkg.exe --triplet x64-windows-static install openssl
Failure logs
Computing installation plan...
The following packages will be built and installed:
openssl[core]:x64-windows-static -> 1.1.1h#3
Detecting compiler hash for triplet x64-windows-static...
Could not locate cached archive: C:\Users\mgcum\AppData\Local\vcpkg\archives\16\169383a1f6432196eefc839d0085ca7c5d72099c.zip
Starting package 1/1: openssl:x64-windows-static
Building package openssl[core]:x64-windows-static...
-- Using cached C:/vcpkg/vcpkg/downloads/openssl-1.1.1h.tar.gz
-- Cleaning sources at C:/vcpkg/vcpkg/buildtrees/openssl/src/openssl-1-09fb822c56.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source C:/vcpkg/vcpkg/downloads/openssl-1.1.1h.tar.gz
-- Using source at C:/vcpkg/vcpkg/buildtrees/openssl/src/openssl-1-09fb822c56.clean
-- Copying openssl release source files...
-- Copying openssl release source files... done
-- Configure x64-windows-static-rel
-- Configure x64-windows-static-rel done
-- Build x64-windows-static-rel
-- Build x64-windows-static-rel done
-- Copying openssl debug source files...
-- Copying openssl debug source files... done
-- Configure x64-windows-static-dbg
-- Configure x64-windows-static-dbg done
-- Build x64-windows-static-dbg
-- Build x64-windows-static-dbg done
CMake Error at scripts/cmake/vcpkg_copy_tool_dependencies.cmake:26 (message):
Could not find PowerShell Core; please open an issue to report this.
Call Stack (most recent call first):
ports/openssl/windows/portfile.cmake:150 (vcpkg_copy_tool_dependencies)
ports/openssl/portfile.cmake:19 (include)
scripts/ports.cmake:136 (include)
Error: Building package openssl:x64-windows-static failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with .\vcpkg update, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
Package: openssl:x64-windows-static
Vcpkg version: 2020.11.12-nohash
Additionally, attach any relevant sections from the log files above.
Additional context
Add any other context about the problem here, such as what you have already tried to resolve the issue.

-- Build x64-windows-static-dbg done
CMake Error at scripts/cmake/vcpkg_copy_tool_dependencies.cmake:26 (message):
>Could not find PowerShell Core; please open an issue to report this.
Call Stack (most recent call first):

When is the last time vcpkg was updated as many changes to the core program (vcpkg.exe) has happened the past few days?
git pull - get the latest vcpkg changes
.\bootstrap-vcpkg.bat - to rebuild the vcpkg binary using updated sources (only needed when [vcpkg-root]\toolsrc files are add, changed and/or deleted)
vcpkg upgrade - to see if any existing packages need upgrading
I just created a fresh new clone and was able to build without any problems?

->.\vcpkg.exe --triplet x64-windows-static install openssl
Computing installation plan...
The following packages will be built and installed:
openssl[core]:x64-windows-static -> 1.1.1h#3
Starting package 1/1: openssl:x64-windows-static
Building package openssl[core]:x64-windows-static...
-- Downloading https://www.openssl.org/source/openssl-1.1.1h.tar.gz...
-- Downloading https://strawberry.perl.bot/download/5.30.0.1/strawberry-perl-5.30.0.1-32bit.zip...
-- Downloading https://strawberry.perl.bot/download/5.30.0.1/strawberry-perl-5.30.0.1-32bit.zip... Failed. Status: 22;"HTTP response code said error"
-- Downloading http://strawberryperl.com/download/5.30.0.1/strawberry-perl-5.30.0.1-32bit.zip...
-- Extracting source D:/Git/vcpkg/test/downloads/openssl-1.1.1h.tar.gz
-- Using source at D:/Git/vcpkg/test/buildtrees/openssl/src/openssl-1-09fb822c56.clean
-- Downloading https://www.nasm.us/pub/nasm/releasebuilds/2.14.02/win32/nasm-2.14.02-win32.zip...
-- Downloading https://download.qt.io/official_releases/jom/jom_1_1_3.zip...
-- Copying openssl release source files...
-- Copying openssl release source files... done
-- Configure x64-windows-static-rel
-- Configure x64-windows-static-rel done
-- Build x64-windows-static-rel
-- Build x64-windows-static-rel done
-- Copying openssl debug source files...
-- Copying openssl debug source files... done
-- Configure x64-windows-static-dbg
-- Configure x64-windows-static-dbg done
-- Build x64-windows-static-dbg
-- Build x64-windows-static-dbg done
-- Installing: D:/Git/vcpkg/test/packages/openssl_x64-windows-static/share/openssl/copyright
-- Installing: D:/Git/vcpkg/test/packages/openssl_x64-windows-static/share/openssl//usage
-- Performing post-build validation
-- Performing post-build validation done
Building package openssl[core]:x64-windows-static... done
Installing package openssl[core]:x64-windows-static...
Installing package openssl[core]:x64-windows-static... done
Elapsed time for package openssl:x64-windows-static: 1.423 min
Total elapsed time: 1.431 min
The package openssl is compatible with built-in CMake targets:
find_package(OpenSSL REQUIRED)
target_link_libraries(main PRIVATE OpenSSL::SSL OpenSSL::Crypto)

Just installed it a few hours ago so I'm pretty sure I have the latest version. Actual just grabbed it again like 2 hours ago to try build again after wiping directory and still doesn't build

Are we STILL having issues building OpenSSL from source on Windows?

Could not find PowerShell Core; please open an issue to report this.

Why you need PowerShell to build OpenSSL? I'm pretty sure I built OpenSSL on Windows without PowerShell!
@Dragonrun1 Have you tried other alternatives? (e.g. nmake, etc)

I have no idea why vcpkg would need PowerShell to build on Windows I just know for some reason someone decided it does in vcpkg.
So some more background on what I'm doing when I ran into the bug. I'm trying to install in rust's cargo a diesel-cli tool which uses a crate called mysqlclient-sys which looks for a static build of the mysql client library. One way it tries to find it is by using vcpkg. vcpkg when you do vcpkg.exe --triplet x64-windows-static install requires openssl to be built which is now broken thus this issue.
I've also done a little testing and this also break stuff for the PostgreSQL build as well since it also require openssl as part of it's build which is not surprising since almost everything in open source uses openssl for anything SSL related.
I notice the version of openssl you have is actually outdate compared to what vcpkg tries to build which is the 1.1.1h version.
So to sum it up have OpenSSL not working in vcpkg breaks almost everything security related in Windows that is trying to use it again!

I would try:

delete file [vcpkg-root]\downloads\PowerShell-7.0.3-win-x86.zip
deleting directory [vcpkg-root]\downloads\tools\powershell-core-7.0.3-windows
install openssl again

This should force vcpkg to download/install powershell core again.

Actuallyu right now neither exists on my system but I was trying some other ideas I found floating around the Internet so I'll for the 4-5? time delete my vcpkg root directory and start over. It'll only take another couple hours to see if it helps ;)

So everything downloaded faster today for me but OpenSSL failed again and there is nothing in downloads directory with PowerShell in it's name so that might be why it can't find it ;)

Is there a powershell directory in your PATH env variable?
C:\Windows\System32\WindowsPowerShell\v1.0\ should be there, any others should be removed, if the directory does not exist.
Try downloading it from https://github.com/PowerShell/PowerShell/releases/download/v7.0.3/PowerShell-7.0.3-win-x86.zip and putting the file in [vcpkg-root]\downloads - make sure to name the file PowerShell-7.0.3-win-x86.zip

Vcpkg should download a copy of PowerShell Core during first use of vcpkg install, e.g.:
A suitable version of powershell-core was not found (required v7.0.3). Downloading portable powershell-core v7.0.3...
Downloading powershell-core...
  https://github.com/PowerShell/PowerShell/releases/download/v7.0.3/PowerShell-7.0.3-win-x86.zip -> E:\Dev\Source\vcpkg\downloads\PowerShell-7.0.3-win-x86.zip
Extracting powershell-core...

Do you see that message when running vcpkg install openssl?
PowerShell Core is required by vcpkg_copy_tool_dependencies() in order to run applocal.ps1. OpenSSL produces an executable OpenSSL.exe, the applocal.ps1script detects which .dll are required for the executable to run and copies those DLLs to the same directory as the executable.
If you don't have a need for OpenSSL.exe produced by the OpenSSL port, a quick patch would be to comment the call to vcpkg_copy_tool_dependencies() from ports/openssl/windows/portfile.cmake.

C:\Windows\System32\WindowsPowerShell\v1.0\ is where it's finding PS5 which was causing the problem.

Another issue with vcpkg_copy_tool_dependencies...
@ras0219 @BillyONeal Please consider to fix this issue first.
Duplicated to #12849.

authors: Dragonrun1 JackBoosY StarGate-One sfhacker vicroms


text:
[New Port Request] libvlcpp

Library name: libvlcpp
Library description:  libvlcpp is a header-only, C++ bindings for the libvlc crossplatform multimedia API. It is an official binding over the VideoLAN libvlc library and can be used on many platforms.  libVLC is the core engine and the interface to the multimedia framework on which VLC media player is based.
libVLC is modularized into hundreds of plugins, which may be loaded at runtime. This architecture provides great flexibility to developers (both VLC devs and devs consuming the library). It allows developers to create a wide range of multimedia applications using the VLC features.
Source repository URL: https://code.videolan.org/videolan/libvlcpp
Project homepage (if different from the source repository): https://www.videolan.org/
Anything else that is useful to know when adding (such as optional features the library may have that should be included):

https://code.videolan.org/videolan/vlc would be needed as a dependency.

@mathisloge Ah, you're right -- and actually, libvlc would meet my purposes just fine, and looks like it's header-only.  Should I go ahead and change the ticket for just libvlc or create a new one?

@morphogencc libvlc isn't header only. libvlcpp is header only. But libvlcpp depends on libvlc.

The ticket thus includes both Libs. And it isn't a big deal to add libvlcpp, but libvlc looks loke a bit more work (to get it right).

Is there any movement on this issue or information I can provide?

If you wish to add this port in the future, you can reopen this issue, but we're closing it for now, consider making a pull request instead.

authors: JackBoosY mathisloge morphogencc


text:
[tiff] Build error

Host Environment

OS: Windows
Compiler: CMake with Visual Studio 2022

To Reproduce
Steps to reproduce the behavior:
./vcpkg install tiff
Additional context
I have installed this before but when I updated vcpkg, i get this error (in log file attached)
"
Error: Failed to download from mirror set:
https://download.osgeo.org/libtiff/tiff-4.3.0.tar.gz: WinHttpSendRequest() failed: 12007
...
Error: Building package tiff:x86-windows failed with: BUILD_FAILED
"
I have tried pinging download.osgeo.org but I get the error "Ping request could not find host download.osgeo.org. Please check the name and try again."
logFile.txt

Check your network. https://download.osgeo.org/libtiff/ is online.

Thanks, must of had been shutdown or smth.


text:
[lapack-reference] Build error

Host Environment

OS: Windows 11
Compiler: cmake

To Reproduce
Steps to reproduce the behavior:
./vcpkg install lapack-reference
Failure logs
PS C:\dev\vcpkg> vcpkg install lapack-reference
Computing installation plan...
The following packages will be built and installed:
    lapack-reference[blas-select,core,noblas]:x86-windows -> 3.10.1
Detecting compiler hash for triplet x86-windows...
-- Setting HTTP_PROXY environment variables to 127.0.0.1:3213
-- Setting HTTPS_PROXY environment variables to 127.0.0.1:3213
Restored 0 packages from C:\Users\Ce\AppData\Local\vcpkg\archives in 122.3 us. Use --debug to see more details.
Installing 1/1 lapack-reference:x86-windows...
Building lapack-reference[blas-select,core,noblas]:x86-windows...
-- Using cached Reference-LAPACK-lapack-v3.10.1.tar.gz.
-- Cleaning sources at C:/dev/vcpkg/buildtrees/lapack-reference/src/v3.10.1-e981a3b485.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source C:/dev/vcpkg/downloads/Reference-LAPACK-lapack-v3.10.1.tar.gz
-- Applying patch lapacke.patch
-- Using source at C:/dev/vcpkg/buildtrees/lapack-reference/src/v3.10.1-e981a3b485.clean
-- The Fortran compiler identification is unknown
-- No Fortran compiler found on the PATH. Using MinGW gfortran!
-- Using cached msys-mingw-w64-i686-gcc-fortran-11.2.0-8-any.pkg.tar.zst.
-- Using cached msys-mingw-w64-i686-gcc-libgfortran-11.2.0-8-any.pkg.tar.zst.
-- Using cached msys-mingw-w64-i686-gcc-libs-11.2.0-8-any.pkg.tar.zst.
-- Using cached msys-mingw-w64-i686-gmp-6.2.1-3-any.pkg.tar.zst.
-- Using cached msys-mingw-w64-i686-libwinpthread-git-9.0.0.6373.5be8fcd83-1-any.pkg.tar.zst.
-- Using cached msys-mingw-w64-i686-winpthreads-git-9.0.0.6373.5be8fcd83-1-any.pkg.tar.zst.
-- Using cached msys-mingw-w64-i686-mpc-1.2.1-1-any.pkg.tar.zst.
-- Using cached msys-mingw-w64-i686-mpfr-4.1.0.p13-1-any.pkg.tar.zst.
-- Using cached msys-mingw-w64-i686-gcc-11.2.0-8-any.pkg.tar.zst.
-- Using cached msys-mingw-w64-i686-binutils-2.37-4-any.pkg.tar.zst.
-- Using cached msys-mingw-w64-i686-crt-git-9.0.0.6373.5be8fcd83-1-any.pkg.tar.zst.
-- Using cached msys-mingw-w64-i686-headers-git-9.0.0.6373.5be8fcd83-1-any.pkg.tar.zst.
-- Using cached msys-mingw-w64-i686-libiconv-1.16-2-any.pkg.tar.zst.
-- Using cached msys-mingw-w64-i686-windows-default-manifest-6.4-3-any.pkg.tar.xz.
-- Using cached msys-mingw-w64-i686-zlib-1.2.11-9-any.pkg.tar.zst.
-- Using cached msys-mingw-w64-i686-zstd-1.5.2-1-any.pkg.tar.zst.
-- Using cached msys-gzip-1.11-1-x86_64.pkg.tar.zst.
-- Using cached msys-bash-5.1.008-1-x86_64.pkg.tar.zst.
-- Using cached msys-diffutils-3.8-2-x86_64.pkg.tar.zst.
-- Using cached msys-coreutils-8.32-2-x86_64.pkg.tar.zst.
-- Using cached msys-grep-3.0-2-x86_64.pkg.tar.xz.
-- Using cached msys-sed-4.8-2-x86_64.pkg.tar.zst.
-- Using cached msys-libpcre-8.45-1-x86_64.pkg.tar.zst.
-- Using cached msys-gawk-5.1.0-2-x86_64.pkg.tar.zst.
-- Using cached msys-mpfr-4.1.0-1-x86_64.pkg.tar.zst.
-- Using cached msys-gmp-6.2.1-1-x86_64.pkg.tar.zst.
-- Using cached msys-libreadline-8.1.001-1-x86_64.pkg.tar.zst.
-- Using cached msys-ncurses-6.2-2-x86_64.pkg.tar.zst.
-- Using cached msys-pkg-config-0.29.2-4-x86_64.pkg.tar.zst.
-- Using cached msys-make-4.3-3-x86_64.pkg.tar.zst.
-- Using cached msys-libintl-0.21-1-x86_64.pkg.tar.zst.
-- Using cached msys-libiconv-1.16-2-x86_64.pkg.tar.zst.
-- Using cached msys-gcc-libs-11.2.0-3-x86_64.pkg.tar.zst.
-- Using cached msys-msys2-runtime-3.2.0-8-x86_64.pkg.tar.zst.
-- Using msys root at C:/dev/vcpkg/downloads/tools/msys2/2b29df0583c528a8
-- Found external ninja('1.10.2').
-- Configuring x86-windows
-- Building x86-windows-dbg
CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:158 (message):
    Command failed: C:/dev/vcpkg/downloads/tools/cmake-3.22.2-windows/cmake-3.22.2-windows-i386/bin/cmake.exe --build . --config Debug --target install -- -v -j13
    Working Directory: C:/dev/vcpkg/buildtrees/lapack-reference/x86-windows-dbg
    See logs for more information:
      C:\dev\vcpkg\buildtrees\lapack-reference\install-x86-windows-dbg-out.log

Call Stack (most recent call first):
  installed/x64-windows/share/vcpkg-cmake/vcpkg_cmake_build.cmake:112 (vcpkg_execute_build_process)
  installed/x64-windows/share/vcpkg-cmake/vcpkg_cmake_install.cmake:41 (vcpkg_cmake_build)
  ports/lapack-reference/portfile.cmake:74 (vcpkg_cmake_install)
  scripts/ports.cmake:146 (include)

error: building lapack-reference:x86-windows failed with: BUILD_FAILED
Please ensure you're using the latest port files with `git pull` and `vcpkg update`.
Then check for known issues at:
    https://github.com/microsoft/vcpkg/issues?q=is%3Aissue+is%3Aopen+in%3Atitle+lapack-reference
You can submit a new issue at:
    https://github.com/microsoft/vcpkg/issues/new?template=report-package-build-failure.md&title=[lapack-reference]+Build+error
Include '[lapack-reference] Build error' in your bug report title, the following version information in your bug description, and attach any relevant failure logs from above.
    vcpkg-tool version: 2022-05-05-67e17c1782801cf481be9ac0b3765dff3e4bdeb8
    vcpkg-scripts version: 20907dc8b 2022-05-25 (8 hours ago)

Additional context
a clean install of the latest vcpkg is used.
vcpkg-tool version: 2022-05-05-67e17c1782801cf481be9ac0b3765dff3e4bdeb8
vcpkg-scripts version: 20907dc8b 2022-05-25 (8 hours ago)

Please provide C:\dev\vcpkg\buildtrees\lapack-reference\install-x86-windows-dbg-out.log first.

Sorry, please see the attached file
install-x86-windows-dbg-out.log

[2502/3793] C:\dev\vcpkg\downloads\tools\msys2\2b29df0583c528a8\mingw32\bin\gfortran.exe -IC:\dev\vcpkg\buildtrees\lapack-reference\src\v3.10.1-e981a3b485.clean\SRC -mabi=ms -m32 -frecursive -g -JSRC -fpreprocessed -c SRC/CMakeFiles/lapack.dir/slartg.f90-pp.f90 -o SRC/CMakeFiles/lapack.dir/slartg.f90.obj
FAILED: SRC/CMakeFiles/lapack.dir/slartg.f90.obj
C:\dev\vcpkg\downloads\tools\msys2\2b29df0583c528a8\mingw32\bin\gfortran.exe -IC:\dev\vcpkg\buildtrees\lapack-reference\src\v3.10.1-e981a3b485.clean\SRC -mabi=ms -m32 -frecursive -g -JSRC -fpreprocessed -c SRC/CMakeFiles/lapack.dir/slartg.f90-pp.f90 -o SRC/CMakeFiles/lapack.dir/slartg.f90.obj
f951.exe: Fatal Error: Reading module 'SRC/la_constants.mod' at line 3 column 10: Unexpected EOF
compilation terminated.

Did you install Visual Studio English Language pack using Visual Studio Installer?

Yes, English language pack is installed in Visual Studio Installer.
The following information might be needed:
Installer version 3.3.1070.38845
Visual Studio Community 2022 Preview 17.2.0 Preview 4.0

I noticed that your vcpkg is out-dated, can you please git pull then try again? If it still fails, please provide the failure log again.
Thanks.

Hi, the vcpkg is the latest one.
PS C:\dev\vcpkg> git pull
Already up to date.
PS C:\dev\vcpkg> .\vcpkg version
vcpkg package management program version 2022-05-05-67e17c1782801cf481be9ac0b3765dff3e4bdeb8

Does your Windows username contain non-ASCII characters or spaces?

Also please provide file C:\dev\vcpkg\buildtrees\lapack-reference\x86-windows-dbg\SRC\la_constants.mod

Hi, my windows username contains no non-ASCII characters or spaces. Since .mod file type is not supported by github, I just compressed it to a zip file.
la_constants.zip

It may be a gfortran bug, but I can't confirm this.

We haven't been able to repro this; if more information comes up, or this issue appears again, please reopen.

So is there a way to fix this, I'm also having this issue。
`CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:134 (message):
Command failed: F:/vcpkg/vcpkg/downloads/tools/cmake-3.25.1-windows/cmake-3.25.1-windows-i386/bin/cmake.exe --build . --config Debug --target install -- -v -j13
Working Directory: F:/vcpkg/vcpkg/buildtrees/lapack-reference/x86-windows-dbg
See logs for more information:
F:\vcpkg\vcpkg\buildtrees\lapack-reference\install-x86-windows-dbg-out.log
Call Stack (most recent call first):
installed/x64-windows/share/vcpkg-cmake/vcpkg_cmake_build.cmake:74 (vcpkg_execute_build_process)
installed/x64-windows/share/vcpkg-cmake/vcpkg_cmake_install.cmake:16 (vcpkg_cmake_build)
ports/lapack-reference/portfile.cmake:77 (vcpkg_cmake_install)
scripts/ports.cmake:147 (include)
error: building lapack-reference:x86-windows failed with: BUILD_FAILED
error: Please ensure you're using the latest port files with git pull and vcpkg update.
Then check for known issues at:
https://github.com/microsoft/vcpkg/issues?q=is%3Aissue+is%3Aopen+in%3Atitle+lapack-reference
You can submit a new issue at:
https://github.com/microsoft/vcpkg/issues/new?template=report-package-build-failure.md&title=[lapack-reference]+Build+error
Include '[lapack-reference] Build error' in your bug report title, the following version information in your bug description, and attach any relevant failure logs from above.
vcpkg-tool version: 2023-01-24-8a88d63f241d391772fbde69af9cab96c3c64c75
vcpkg-scripts version: d5bc0e71e 2023-02-27 (15 hours ago)`

No, I even don't know why it happened.

authors: GISerCHAO JackBoosY shencebebetterme


text:
[wxwidgets] Build error

Host Environment

OS: [Linux Zorin OS]
Compiler: g++ 11

To Reproduce
Steps to reproduce the behavior:
vcpkg install wxwidgets
Failure logs
error: building wxwidgets:x64-linux failed with: BUILD_FAILED
Please ensure you're using the latest port files with git pull and vcpkg update.
Then check for known issues at:
https://github.com/microsoft/vcpkg/issues?q=is%3Aissue+is%3Aopen+in%3Atitle+wxwidgets
You can submit a new issue at:
https://github.com/microsoft/vcpkg/issues/new?template=report-package-build-failure.md&title=[wxwidgets]+Build+error
Include '[wxwidgets] Build error' in your bug report title, the following version information in your bug description, and attach any relevant failure logs from above.
vcpkg-tool version: 2022-06-15-b0f08e40f8e8752dd0b260138ee078bd9599559c
vcpkg-scripts version: 92136965a 2022-06-17 (27 minutes ago)

Please provide the error logs

stdout-x64-linux.log

And
    See logs for more information:
      /opt/vcpkg/buildtrees/wxwidgets/config-x64-linux-dbg-out.log
      /opt/vcpkg/buildtrees/wxwidgets/config-x64-linux-dbg-err.log

config-x64-linux-dbg-err.log
config-x64-linux-dbg-out.log

This is the error:
CMake Error at /opt/vcpkg/scripts/buildsystems/vcpkg.cmake:613 (_add_library):
  Target "wxgl" links to target "OpenGL::GLU" but the target was not found.
  Perhaps a find_package() call is missing for an IMPORTED target, or an
  ALIAS target is missing?
Call Stack (most recent call first):
  build/cmake/functions.cmake:413 (add_library)
  build/cmake/lib/gl/CMakeLists.txt:26 (wx_add_library)

 sudo apt-get install freeglut3-dev
I solved the problem with this. Thank you

authors: autoantwort dg0yt togisoft


text:
[folly] build failure after PR #25335

Prior to https://github.com/microsoft/vcpkg/pull/25335 I used to be able to put folly in vcpkg.json and it would just install
Now when I try to do this on a new project, I get errors about zstd (required from libevent) and unofficial-sodium not being installed 🙁
{
  "$schema": "https://raw.githubusercontent.com/microsoft/vcpkg/master/scripts/vcpkg.schema.json",
  "name": "app",
  "version": "0.0.1",
  "dependencies": ["folly"]
}

-- Running vcpkg install - done
-- Found libevent include directory: /home/user/projects/bustub-cpp-reimpl/cmake-build-debug/vcpkg_installed/x64-linux/include
-- Found libevent component: /home/user/projects/bustub-cpp-reimpl/cmake-build-debug/vcpkg_installed/x64-linux/debug/lib/libevent_core.a
-- Found libevent component: /home/user/projects/bustub-cpp-reimpl/cmake-build-debug/vcpkg_installed/x64-linux/debug/lib/libevent_extra.a
-- Found libevent component: /home/user/projects/bustub-cpp-reimpl/cmake-build-debug/vcpkg_installed/x64-linux/debug/lib/libevent_pthreads.a
-- Found libevent 2.1.12 in /home/user/projects/bustub-cpp-reimpl/cmake-build-debug/vcpkg_installed/x64-linux
CMake Error at cmake-build-debug/_deps/vcpkg-src/scripts/buildsystems/vcpkg.cmake:834 (_find_package):
  Could not find a package configuration file provided by "zstd" with any of
  the following names:

    zstdConfig.cmake
    zstd-config.cmake

  Add the installation prefix of "zstd" to CMAKE_PREFIX_PATH or set
  "zstd_DIR" to a directory containing one of the above files.  If "zstd"
  provides a separate development package or SDK, be sure it has been
  installed.
Call Stack (most recent call first):
  /usr/share/cmake/Modules/CMakeFindDependencyMacro.cmake:47 (find_package)
  cmake-build-debug/vcpkg_installed/x64-linux/share/folly/folly-config.cmake:59 (find_dependency)
  cmake-build-debug/vcpkg_installed/x64-linux/share/folly/vcpkg-cmake-wrapper.cmake:4 (_find_package)
  cmake-build-debug/_deps/vcpkg-src/scripts/buildsystems/vcpkg.cmake:788 (include)
  CMakeLists.txt:28 (find_package)

Now add zstd as dependency:
{
	"dependencies": ["folly", "zstd"]
}

-- Running vcpkg install - done
-- Found libevent include directory: /home/user/projects/bustub-cpp-reimpl/cmake-build-debug/vcpkg_installed/x64-linux/include
-- Found libevent component: /home/user/projects/bustub-cpp-reimpl/cmake-build-debug/vcpkg_installed/x64-linux/debug/lib/libevent_core.a
-- Found libevent component: /home/user/projects/bustub-cpp-reimpl/cmake-build-debug/vcpkg_installed/x64-linux/debug/lib/libevent_extra.a
-- Found libevent component: /home/user/projects/bustub-cpp-reimpl/cmake-build-debug/vcpkg_installed/x64-linux/debug/lib/libevent_pthreads.a
-- Found libevent 2.1.12 in /home/user/projects/bustub-cpp-reimpl/cmake-build-debug/vcpkg_installed/x64-linux
CMake Error at cmake-build-debug/_deps/vcpkg-src/scripts/buildsystems/vcpkg.cmake:834 (_find_package):
  Could not find a package configuration file provided by "unofficial-sodium"
  with any of the following names:

    unofficial-sodiumConfig.cmake
    unofficial-sodium-config.cmake

  Add the installation prefix of "unofficial-sodium" to CMAKE_PREFIX_PATH or
  set "unofficial-sodium_DIR" to a directory containing one of the above
  files.  If "unofficial-sodium" provides a separate development package or
  SDK, be sure it has been installed.
Call Stack (most recent call first):
  /usr/share/cmake/Modules/CMakeFindDependencyMacro.cmake:47 (find_package)
  cmake-build-debug/vcpkg_installed/x64-linux/share/folly/folly-config.cmake:62 (find_dependency)
  cmake-build-debug/vcpkg_installed/x64-linux/share/folly/vcpkg-cmake-wrapper.cmake:4 (_find_package)
  cmake-build-debug/_deps/vcpkg-src/scripts/buildsystems/vcpkg.cmake:788 (include)
  CMakeLists.txt:28 (find_package)

I don't see unofficial-sodium in vcpkg list so what am I supposed to do now?
🙁

unofficial-sodium comes from port libsodium.
Port folly hides these dependencies behind features (at build time), but unfortunately the patches don't take care of feature controllers when exporting CMake config.

Can confirm that adding libsodium to vcpkg.json makes folly build again, ty!


text:
[libiconv] Build error

Host Environment

OS: Windows 10
Compiler: VS19

To Reproduce
Steps to reproduce the behavior:
vcpkg install opencv[eigen,ffmpeg,webp,contrib,nonFree,cuda] --triplet x64-windows
Failure logs
Console Output
Computing installation plan...
The following packages will be built and installed:

libarchive[bzip2,core,libxml2,lz4,lzma,openssl,zstd]:x64-windows -> 3.6.1#1
libiconv[core]:x64-windows -> 1.17
libxml2[core]:x64-windows -> 2.10.3
opencv[contrib,core,cuda,default-features,eigen,ffmpeg,nonfree,webp]:x64-windows -> 4.6.0
opencv4[contrib,core,cuda,default-features,dnn,eigen,ffmpeg,jpeg,nonfree,png,quirc,tiff,webp]:x64-windows -> 4.6.0#10
openssl[core]:x64-windows -> 3.0.7#1
protobuf[core]:x64-windows -> 3.21.8
quirc[core]:x64-windows -> 1.1#3
tesseract[core]:x64-windows -> 5.2.0#3
vcpkg-get-python-packages[core]:x64-windows -> 2022-06-30
Additional packages (*) will be modified to complete this operation.
Detecting compiler hash for triplet x64-windows...
Restored 0 package(s) from C:\Users\jakob.ropers\AppData\Local\vcpkg\archives in 2.224 ms. Use --debug to see more details.
Installing 1/10 libiconv:x64-windows...
Building libiconv[core]:x64-windows...
-- Using cached libiconv-1.17.tar.gz.
-- Cleaning sources at C:/CODING/MeshroomDepthMOD/vcpkg/buildtrees/libiconv/src/1.17-e2a53830aa.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source C:/CODING/MeshroomDepthMOD/vcpkg/downloads/libiconv-1.17.tar.gz
-- Applying patch 0002-Config-for-MSVC.patch
-- Applying patch 0003-Add-export.patch
-- Applying patch 0004-ModuleFileName.patch
-- Using source at C:/CODING/MeshroomDepthMOD/vcpkg/buildtrees/libiconv/src/1.17-e2a53830aa.clean
-- Found external ninja('1.10.2').
-- Getting CMake variables for x64-windows
-- Using cached msys-gzip-1.11-1-x86_64.pkg.tar.zst.
-- Using cached msys-bash-5.1.008-1-x86_64.pkg.tar.zst.
-- Using cached msys-autoconf-2.71-3-any.pkg.tar.zst.
-- Using cached msys-diffutils-3.8-2-x86_64.pkg.tar.zst.
-- Using cached msys-binutils-2.37-5-x86_64.pkg.tar.zst.
-- Using cached msys-libtool-2.4.6-9-x86_64.pkg.tar.xz.
-- Using cached msys-file-5.41-2-x86_64.pkg.tar.zst.
-- Using cached msys-zlib-1.2.11-1-x86_64.pkg.tar.xz.
-- Using cached msys-libbz2-1.0.8-3-x86_64.pkg.tar.zst.
-- Using cached msys-coreutils-8.32-2-x86_64.pkg.tar.zst.
-- Using cached msys-grep-3.0-2-x86_64.pkg.tar.xz.
-- Using cached msys-sed-4.8-2-x86_64.pkg.tar.zst.
-- Using cached msys-libpcre-8.45-1-x86_64.pkg.tar.zst.
-- Using cached msys-m4-1.4.19-2-x86_64.pkg.tar.zst.
-- Using cached msys-automake-wrapper-11-4-any.pkg.tar.zst.
-- Using cached msys-gawk-5.1.0-2-x86_64.pkg.tar.zst.
-- Using cached msys-mpfr-4.1.0-1-x86_64.pkg.tar.zst.
-- Using cached msys-gmp-6.2.1-1-x86_64.pkg.tar.zst.
-- Using cached msys-libreadline-8.1.001-1-x86_64.pkg.tar.zst.
-- Using cached msys-ncurses-6.2-2-x86_64.pkg.tar.zst.
-- Using cached msys-automake1.16-1.16.3-3-any.pkg.tar.zst.
-- Using cached msys-perl-5.32.1-2-x86_64.pkg.tar.zst.
-- Using cached msys-libcrypt-2.1-3-x86_64.pkg.tar.zst.
-- Using cached msys-pkg-config-0.29.2-4-x86_64.pkg.tar.zst.
-- Using cached msys-make-4.3-3-x86_64.pkg.tar.zst.
-- Using cached msys-findutils-4.8.0-1-x86_64.pkg.tar.zst.
-- Using cached msys-libintl-0.21-1-x86_64.pkg.tar.zst.
-- Using cached msys-libiconv-1.16-2-x86_64.pkg.tar.zst.
-- Using cached msys-gcc-libs-11.2.0-3-x86_64.pkg.tar.zst.
-- Using cached msys-msys2-runtime-3.2.0-8-x86_64.pkg.tar.zst.
-- Using cached msys-which-2.21-4-x86_64.pkg.tar.zst.
-- Using msys root at C:/CODING/MeshroomDepthMOD/vcpkg/downloads/tools/msys2/583ad6e4115a307a
-- Using cached msys-mingw-w64-i686-pkg-config-0.29.2-3-any.pkg.tar.zst.
-- Using cached msys-mingw-w64-i686-libwinpthread-git-9.0.0.6373.5be8fcd83-1-any.pkg.tar.zst.
-- Using msys root at C:/CODING/MeshroomDepthMOD/vcpkg/downloads/tools/msys2/9a1ec3f33446b195
-- Configuring x64-windows-dbg
-- Configuring x64-windows-rel
-- Building x64-windows-dbg
CMake Warning at scripts/cmake/vcpkg_execute_build_process.cmake:62 (message):
Please ensure your system has sufficient memory.
Call Stack (most recent call first):
scripts/cmake/vcpkg_build_make.cmake:149 (vcpkg_execute_build_process)
scripts/cmake/vcpkg_install_make.cmake:2 (vcpkg_build_make)
ports/libiconv/portfile.cmake:39 (vcpkg_install_make)
scripts/ports.cmake:147 (include)

-- Restarting build without parallelism
CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:131 (message):
Command failed: C:/CODING/MeshroomDepthMOD/vcpkg/downloads/tools/msys2/583ad6e4115a307a/usr/bin/make.exe -j 17 --trace -f Makefile all
Working Directory: C:/CODING/MeshroomDepthMOD/vcpkg/buildtrees/libiconv/x64-windows-dbg/
See logs for more information:
C:\CODING\MeshroomDepthMOD\vcpkg\buildtrees\libiconv\build-x64-windows-dbg-out.log
C:\CODING\MeshroomDepthMOD\vcpkg\buildtrees\libiconv\build-x64-windows-dbg-err.log
C:\CODING\MeshroomDepthMOD\vcpkg\buildtrees\libiconv\build-x64-windows-dbg-out-1.log
C:\CODING\MeshroomDepthMOD\vcpkg\buildtrees\libiconv\build-x64-windows-dbg-err-1.log
Call Stack (most recent call first):
scripts/cmake/vcpkg_build_make.cmake:149 (vcpkg_execute_build_process)
scripts/cmake/vcpkg_install_make.cmake:2 (vcpkg_build_make)
ports/libiconv/portfile.cmake:39 (vcpkg_install_make)
scripts/ports.cmake:147 (include)
build-x64-windows-dbg-out.log
Makefile:41: target 'lib/localcharset.h' does not exist
builddir="pwd"; cd libcharset && /usr/bin/make all && /usr/bin/make install-lib libdir="$builddir/lib" includedir="$builddir/lib"
make[1]: Entering directory '/c/CODING/MeshroomDepthMOD/vcpkg/buildtrees/libiconv/x64-windows-dbg/libcharset'
Makefile:34: update target 'all' due to: force
cd lib && /usr/bin/make all
make[2]: Entering directory '/c/CODING/MeshroomDepthMOD/vcpkg/buildtrees/libiconv/x64-windows-dbg/libcharset/lib'
Makefile:58: update target 'localcharset.lo' due to: ../.././../src/1.17-e2a53830aa.clean/libcharset/lib/localcharset.c
/bin/sh ../libtool --mode=compile compile cl.exe -I. -I../.././../src/1.17-e2a53830aa.clean/libcharset/lib -I.. -I../.././../src/1.17-e2a53830aa.clean/libcharset/lib/.. -I../include -nologo -W3 -utf-8 -MP -MDd -Z7 -Ob0 -Od -Xcompiler -RTC1  -DWIN32 -D_WINDOWS -D_DEBUG -DBUILDING_LIBCHARSET -DHAVE_CONFIG_H -c ../.././../src/1.17-e2a53830aa.clean/libcharset/lib/localcharset.c
Makefile:61: update target 'relocatable-stub.lo' due to: ../.././../src/1.17-e2a53830aa.clean/libcharset/lib/relocatable-stub.c
/bin/sh ../libtool --mode=compile compile cl.exe -I. -I../.././../src/1.17-e2a53830aa.clean/libcharset/lib -I.. -I../.././../src/1.17-e2a53830aa.clean/libcharset/lib/.. -I../include -nologo -W3 -utf-8 -MP -MDd -Z7 -Ob0 -Od -Xcompiler -RTC1  -DWIN32 -D_WINDOWS -D_DEBUG -DBUILDING_LIBCHARSET -DHAVE_CONFIG_H -c ../.././../src/1.17-e2a53830aa.clean/libcharset/lib/relocatable-stub.c
libtool: compile:  compile cl.exe -I. -I../.././../src/1.17-e2a53830aa.clean/libcharset/lib -I.. -I../.././../src/1.17-e2a53830aa.clean/libcharset/lib/.. -I../include -nologo -W3 -utf-8 -MP -MDd -Z7 -Ob0 -RTC1 -Od -DWIN32 -D_WINDOWS -D_DEBUG -DBUILDING_LIBCHARSET -DHAVE_CONFIG_H -c ../.././../src/1.17-e2a53830aa.clean/libcharset/lib/localcharset.c  -DDLL_EXPORT -DPIC -o .libs/localcharset.obj
libtool: compile:  compile cl.exe -I. -I../.././../src/1.17-e2a53830aa.clean/libcharset/lib -I.. -I../.././../src/1.17-e2a53830aa.clean/libcharset/lib/.. -I../include -nologo -W3 -utf-8 -MP -MDd -Z7 -Ob0 -RTC1 -Od -DWIN32 -D_WINDOWS -D_DEBUG -DBUILDING_LIBCHARSET -DHAVE_CONFIG_H -c ../.././../src/1.17-e2a53830aa.clean/libcharset/lib/relocatable-stub.c  -DDLL_EXPORT -DPIC -o .libs/relocatable-stub.obj
relocatable-stub.c
localcharset.c
../.././../src/1.17-e2a53830aa.clean/libcharset/lib/localcharset.c(929): warning C4996: 'sprintf': This function or variable may be unsafe. Consider using sprintf_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details.
../.././../src/1.17-e2a53830aa.clean/libcharset/lib/localcharset.c(939): warning C4996: 'sprintf': This function or variable may be unsafe. Consider using sprintf_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details.
../.././../src/1.17-e2a53830aa.clean/libcharset/lib/localcharset.c(947): warning C4996: 'strcpy': This function or variable may be unsafe. Consider using strcpy_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details.
Makefile:55: update target 'libcharset.la' due to: localcharset.lo relocatable-stub.lo
/bin/sh ../libtool --mode=link compile cl.exe -Xlinker -Xlinker -Xlinker -LC:/CODING/MeshroomDepthMOD/vcpkg/installed/x64-windows/debug/lib -Xlinker -Xlinker -Xlinker -machine:x64 -Xlinker -Xlinker -Xlinker -nologo -Xlinker -Xlinker -Xlinker -debug -Xlinker -Xlinker -Xlinker -INCREMENTAL -nologo -W3 -utf-8 -MP -MDd -Z7 -Ob0 -Od -Xcompiler -RTC1  -o libcharset.la -rpath /C/CODING/MeshroomDepthMOD/vcpkg/installed/x64-windows/debug/lib -version-info 1:0:0 -no-undefined localcharset.lo relocatable-stub.lo
libtool: link: dumpbin.exe -symbols -headers  .libs/localcharset.obj .libs/relocatable-stub.obj   | gawk '     {last_section=section; section=$ 3};     /^COFF SYMBOL TABLE/{for(i in hide) delete hide[i]};     /Section length .#relocs.(pick any)/{hide[last_section]=1};     /^ *Symbol name *: /{split($ 0,sn,":"); si=substr(sn[2],2)};     /^ Type : code/{print "T",si,substr(si,length(prfx))};     /^ Type : data/{print "I",si,substr(si,length(prfx))};     $ 0!~/External |/{next};     / 0+ UNDEF /{next}; / UNDEF ([^|])()/{next};     {if(hide[section]) next};     {f="D"}; $ 0~/().|/{f="T"};     {split($ 0,a,/||\r/); split(a[2],s)};     s[1]~/^[@?]/{print f,s[1],s[1]; next};     s[1]~prfx {split(s[1],t,"@"); print f,t[1],substr(t[1],length(prfx))}     ' prfx=^ | /usr/bin/sed '/ __gnu_lto/d' | /usr/bin/sed -e '/^[BCDGRS][ ]/s/.[ ]([^ ])/\1,DATA/' | /usr/bin/sed -e '/^[AITW][ ]/s/.[ ]//' | sort | uniq > .libs/charset.exp
libtool: link: if test DEF = "/usr/bin/sed -n -e 's/^[	 ]*//' -e '/^\(;.*\)*$/d' -e 's/^\(EXPORTS\|LIBRARY\)\([	 ].*\)*$/DEF/p' -e q .libs/charset.exp" ; then cp ".libs/charset.exp" ".libs/charset-1.dll.def"; echo "WARNING! VENV_PATH is not defined!!!
libtool: link: .libs\charset-1.dll.def" > ".libs/charset-1.dll.exp"; else /usr/bin/sed -e 's/^/-link -EXPORT:/' < .libs/charset.exp > .libs/charset-1.dll.exp; fi
libtool: link:  compile cl.exe -o WARNING! VENV_PATH is not defined!!!
libtool: link: .libs\charset-1.dll  .libs/localcharset.obj .libs/relocatable-stub.obj   -Xlinker -LC:/CODING/MeshroomDepthMOD/vcpkg/installed/x64-windows/debug/lib -Xlinker -machine:x64 -Xlinker -nologo -Xlinker -debug -Xlinker -INCREMENTAL -Ob0 -Od -RTC1    "@WARNING! VENV_PATH is not defined!!!
libtool: link: .libs\charset-1.dll.exp" -Wl,-DLL,-IMPLIB:"WARNING! VENV_PATH is not defined!!!
libtool: link: .libs\charset.lib"
LINK : fatal error LNK1104: cannot open file 'VENV_PATH.obj'
make[2]: Leaving directory '/c/CODING/MeshroomDepthMOD/vcpkg/buildtrees/libiconv/x64-windows-dbg/libcharset/lib'
make[1]: Leaving directory '/c/CODING/MeshroomDepthMOD/vcpkg/buildtrees/libiconv/x64-windows-dbg/libcharset'
build-x64-windows-dbg-err.log
Microsoft (R) C/C++ Optimizing Compiler Version 19.29.30147 for x64
Copyright (C) Microsoft Corporation.  All rights reserved.
cl : Command line warning D9024 : unrecognized source file type 'VENV_PATH', object file assumed
cl : Command line warning D9024 : unrecognized source file type 'is', object file assumed
cl : Command line warning D9024 : unrecognized source file type 'not', object file assumed
cl : Command line warning D9024 : unrecognized source file type 'defined!!!', object file assumed
../libtool: line 10858: .libs\charset-1.dll: No such file or directory
make[2]: *** [Makefile:55: libcharset.la] Error 127
make[1]: *** [Makefile:34: all] Error 2
make: *** [Makefile:41: lib/localcharset.h] Error 2
build-x64-windows-dbg-out-1.log
Makefile:41: target 'lib/localcharset.h' does not exist
builddir="pwd"; cd libcharset && /usr/bin/make all && /usr/bin/make install-lib libdir="$builddir/lib" includedir="$builddir/lib"
make[1]: Entering directory '/c/CODING/MeshroomDepthMOD/vcpkg/buildtrees/libiconv/x64-windows-dbg/libcharset'
Makefile:34: update target 'all' due to: force
cd lib && /usr/bin/make all
make[2]: Entering directory '/c/CODING/MeshroomDepthMOD/vcpkg/buildtrees/libiconv/x64-windows-dbg/libcharset/lib'
Makefile:55: update target 'libcharset.la' due to: localcharset.lo relocatable-stub.lo
/bin/sh ../libtool --mode=link compile cl.exe -Xlinker -Xlinker -Xlinker -LC:/CODING/MeshroomDepthMOD/vcpkg/installed/x64-windows/debug/lib -Xlinker -Xlinker -Xlinker -machine:x64 -Xlinker -Xlinker -Xlinker -nologo -Xlinker -Xlinker -Xlinker -debug -Xlinker -Xlinker -Xlinker -INCREMENTAL -nologo -W3 -utf-8 -MP -MDd -Z7 -Ob0 -Od -Xcompiler -RTC1  -o libcharset.la -rpath /C/CODING/MeshroomDepthMOD/vcpkg/installed/x64-windows/debug/lib -version-info 1:0:0 -no-undefined localcharset.lo relocatable-stub.lo
libtool: link: rm -fr  .libs/charset.exp
libtool: link: dumpbin.exe -symbols -headers  .libs/localcharset.obj .libs/relocatable-stub.obj   | gawk '     {last_section=section; section=$ 3};     /^COFF SYMBOL TABLE/{for(i in hide) delete hide[i]};     /Section length .#relocs.(pick any)/{hide[last_section]=1};     /^ *Symbol name *: /{split($ 0,sn,":"); si=substr(sn[2],2)};     /^ Type : code/{print "T",si,substr(si,length(prfx))};     /^ Type : data/{print "I",si,substr(si,length(prfx))};     $ 0!~/External |/{next};     / 0+ UNDEF /{next}; / UNDEF ([^|])()/{next};     {if(hide[section]) next};     {f="D"}; $ 0~/().|/{f="T"};     {split($ 0,a,/||\r/); split(a[2],s)};     s[1]~/^[@?]/{print f,s[1],s[1]; next};     s[1]~prfx {split(s[1],t,"@"); print f,t[1],substr(t[1],length(prfx))}     ' prfx=^ | /usr/bin/sed '/ __gnu_lto/d' | /usr/bin/sed -e '/^[BCDGRS][ ]/s/.[ ]([^ ])/\1,DATA/' | /usr/bin/sed -e '/^[AITW][ ]/s/.[ ]//' | sort | uniq > .libs/charset.exp
libtool: link: if test DEF = "/usr/bin/sed -n -e 's/^[	 ]*//' -e '/^\(;.*\)*$/d' -e 's/^\(EXPORTS\|LIBRARY\)\([	 ].*\)*$/DEF/p' -e q .libs/charset.exp" ; then cp ".libs/charset.exp" ".libs/charset-1.dll.def"; echo "WARNING! VENV_PATH is not defined!!!
libtool: link: .libs\charset-1.dll.def" > ".libs/charset-1.dll.exp"; else /usr/bin/sed -e 's/^/-link -EXPORT:/' < .libs/charset.exp > .libs/charset-1.dll.exp; fi
libtool: link:  compile cl.exe -o WARNING! VENV_PATH is not defined!!!
libtool: link: .libs\charset-1.dll  .libs/localcharset.obj .libs/relocatable-stub.obj   -Xlinker -LC:/CODING/MeshroomDepthMOD/vcpkg/installed/x64-windows/debug/lib -Xlinker -machine:x64 -Xlinker -nologo -Xlinker -debug -Xlinker -INCREMENTAL -Ob0 -Od -RTC1    "@WARNING! VENV_PATH is not defined!!!
libtool: link: .libs\charset-1.dll.exp" -Wl,-DLL,-IMPLIB:"WARNING! VENV_PATH is not defined!!!
libtool: link: .libs\charset.lib"
LINK : fatal error LNK1104: cannot open file 'VENV_PATH.obj'
make[2]: Leaving directory '/c/CODING/MeshroomDepthMOD/vcpkg/buildtrees/libiconv/x64-windows-dbg/libcharset/lib'
make[1]: Leaving directory '/c/CODING/MeshroomDepthMOD/vcpkg/buildtrees/libiconv/x64-windows-dbg/libcharset'
build-x64-windows-dbg-err-1.log
Microsoft (R) C/C++ Optimizing Compiler Version 19.29.30147 for x64
Copyright (C) Microsoft Corporation.  All rights reserved.
cl : Command line warning D9024 : unrecognized source file type 'VENV_PATH', object file assumed
cl : Command line warning D9024 : unrecognized source file type 'is', object file assumed
cl : Command line warning D9024 : unrecognized source file type 'not', object file assumed
cl : Command line warning D9024 : unrecognized source file type 'defined!!!', object file assumed
../libtool: line 10858: .libs\charset-1.dll: No such file or directory
make[2]: *** [Makefile:55: libcharset.la] Error 127
make[1]: *** [Makefile:34: all] Error 2
make: *** [Makefile:41: lib/localcharset.h] Error 2
Additional context
As instructed, I tried "git pull" followed by "vcpkg update". This did not help.

vcpkg-tool version: 2022-12-14-7ae0d8527fb488fde10a89c2813802dc9b03b6f9
vcpkg-scripts version: 71f51b100 2022-12-17 (4 weeks ago)

Thanks for reporting this issue, but I can't reproduce it in my side with the latest vcpkg.
I see that the errors in your log are related to libtool. Because this tool has been updated recently, could you please remove the vcpkg/downloads folder and run following command again? Thank you!
.\vcpkg.exe install libiconv:x64-windows --bianrysource=clear

Thank you for the quick reply Cheney. I am still getting an error after trying this...

I am also running into an error building libiconv, but in my case it seems like it's trying to pull down deps that don't exist anymore, specifically an old version of libtool:
error: Failed to download from mirror set
error: https://repo.msys2.org/msys/x86_64/libtool-2.4.6-9-x86_64.pkg.tar.xz: failed: status code 404
error: https://www2.futureware.at/~nickoe/msys2-mirror/msys/x86_64/libtool-2.4.6-9-x86_64.pkg.tar.xz: failed: status code 404
error: https://mirror.yandex.ru/mirrors/msys2/msys/x86_64/libtool-2.4.6-9-x86_64.pkg.tar.xz: failed: status code 404
error: https://mirrors.tuna.tsinghua.edu.cn/msys2/msys/x86_64/libtool-2.4.6-9-x86_64.pkg.tar.xz: failed: status code 404
error: https://mirrors.ustc.edu.cn/msys2/msys/x86_64/libtool-2.4.6-9-x86_64.pkg.tar.xz: failed: status code 404
error: https://mirror.bit.edu.cn/msys2/msys/x86_64/libtool-2.4.6-9-x86_64.pkg.tar.xz: WinHttpSendRequest failed with exit code 12007
error: https://mirror.bit.edu.cn/msys2/msys/x86_64/libtool-2.4.6-9-x86_64.pkg.tar.xz: WinHttpSendRequest failed with exit code 12007
error: https://mirror.bit.edu.cn/msys2/msys/x86_64/libtool-2.4.6-9-x86_64.pkg.tar.xz: WinHttpSendRequest failed with exit code 12007
error: https://mirror.bit.edu.cn/msys2/msys/x86_64/libtool-2.4.6-9-x86_64.pkg.tar.xz: WinHttpSendRequest failed with exit code 12007
error: https://mirror.selfnet.de/msys2/msys/x86_64/libtool-2.4.6-9-x86_64.pkg.tar.xz: failed: status code 404
error: https://mirrors.sjtug.sjtu.edu.cn/msys2/msys/x86_64/libtool-2.4.6-9-x86_64.pkg.tar.xz: failed: status code 404

Version 2.4.6-9 does not exist on those mirrors...

@ooshlablu Update your vcpkg repo (git pull, bootstrap-vcpkg).

I had my version pinned to the latest release (2023.01.09) which is why I wasn't getting the fix. The issue was identified and resolved a week after that release, so naturally changing to master fixed it for now. We will be able to pin to future releases.
Thanx!

@Cheney-W can be closed now.

authors: Cheney-W JackBoosY dg0yt jakob-ropers-snkeos ooshlablu


text:
[boost-core] build failure in release 2024.05.24 - Failed to download from mirror set/File does not have the expected hash

Operating system
Windows
Compiler
msvc (Visual Studio 17.10)
Steps to reproduce the behavior
vcpkg.json file contents:

{
  "$schema": "https://raw.githubusercontent.com/microsoft/vcpkg-tool/main/docs/vcpkg.schema.json",
  "dependencies": [
    "boost-algorithm",
    "boost-json",
    "boost-program-options",
    "boost-property-tree"
  ],
  "builtin-baseline": "01f602195983451bc83e72f4214af2cbc495aa94"
}

The baseline is the commit hash for 2024.05.24.

### Failure logs

vcpkg output:
-- Config win-x64-debug doesn't require any special settings. CMake will use its defaults for the host system.
-- Bootstrapping vcpkg before install
-- Bootstrapping vcpkg before install - done
-- Running vcpkg install
A suitable version of cmake was not found (required v3.29.2) Downloading portable cmake 3.29.2...
Downloading cmake...
https://github.com/Kitware/CMake/releases/download/v3.29.2/cmake-3.29.2-windows-i386.zip->C:\git\client-native-host\external\vcpkg\downloads\cmake-3.29.2-windows-i386.zip
Downloading https://github.com/Kitware/CMake/releases/download/v3.29.2/cmake-3.29.2-windows-i386.zip
Extracting cmake...
Detecting compiler hash for triplet x64-windows...
Compiler found: C:/Program Files/Microsoft Visual Studio/2022/Enterprise/VC/Tools/MSVC/14.40.33807/bin/HostX64/x64/cl.exe
The following packages will be built and installed:
    boost-algorithm:x64-windows@1.85.0 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-algorithm\289b704f6e8d17b2d63d1dcdd077eafe38b9c650
  * boost-align:x64-windows@1.85.0 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-align\0c748701339f94c1721d1bb574bb4afeaa77af9b
  * boost-any:x64-windows@1.85.0 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-any\a2426759d8f50ced5428ec22680f7010f7476ae1
  * boost-array:x64-windows@1.85.0 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-array\887dfc0b92387a7232cb1479e19be910521233e8
  * boost-assert:x64-windows@1.85.0 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-assert\2720690553c459c12a23f54451fe9c9f1d96164c
  * boost-atomic:x64-windows@1.85.0 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-atomic\98b9c0f27deafd4cb4a361c0836368cc6f4025a1
  * boost-bind:x64-windows@1.85.0 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-bind\3ef8c61e78989d8c9b7e57e63e23a4291822b0a3
  * boost-chrono:x64-windows@1.85.0 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-chrono\e6767fb8800ff117606a75e474255bff566f8eef
  * boost-cmake:x64-windows@1.85.0 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-cmake\bb385ffc8aa74989b8198a777f3181b3a209451a
  * boost-concept-check:x64-windows@1.85.0 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-concept-check\36c59f199a9c35fc69d4b1f6f57d580cb74e3172
  * boost-config:x64-windows@1.85.0 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-config\9c454bf1a50c40d4025fe2ee6edc21720cf39c9e
  * boost-container:x64-windows@1.85.0#1 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-container\b304461cda37cd06d1097cc5135c3eb178eb5036
  * boost-container-hash:x64-windows@1.85.0 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-container-hash\c61380aa9e806ea8b8a4995b416001696a6707d6
  * boost-conversion:x64-windows@1.85.0 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-conversion\10cb3d14697a464f78d2f6e37a81237644ee1427
  * boost-core:x64-windows@1.85.0 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-core\195375664be82cbc16178de90096e451de070d80
  * boost-date-time:x64-windows@1.85.0 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-date-time\f74823cc33c643986ea5b190b7c8b2899276e7f1
  * boost-describe:x64-windows@1.85.0 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-describe\5bf8efca10586773cb73e95aad3cecdcff0ea57c
  * boost-detail:x64-windows@1.85.0 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-detail\8b766b66fa3a803b677efde5b4c7eed9e4fdd9e1
  * boost-endian:x64-windows@1.85.0 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-endian\2a1be7e6b3a7db7c7bdc8906d02b719c413b8def
  * boost-exception:x64-windows@1.85.0 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-exception\6b90844360d52f77e060176e0ba59c2b6b585bb9
  * boost-function:x64-windows@1.85.0 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-function\f10fc77f4c0597464acde55225177170865e48be
  * boost-function-types:x64-windows@1.85.0 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-function-types\92c14af0950ae5db39914882838c80a8e33cae5b
  * boost-functional:x64-windows@1.85.0 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-functional\c944ab99b7e422142adb594b89964a20269b4904
  * boost-fusion:x64-windows@1.85.0 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-fusion\91d988664a3d7b4ff92f2b22b9907c04f004d066
  * boost-headers:x64-windows@1.85.0 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-headers\6cf27bbd161498aef1c033c3b3951b27c6f430b7
  * boost-integer:x64-windows@1.85.0 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-integer\734270e5c00d151f6f41c1e9cd325c0c7ae58ea3
  * boost-intrusive:x64-windows@1.85.0 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-intrusive\786765661875cab1398c3170ef649284b558d2b4
  * boost-io:x64-windows@1.85.0 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-io\d6bd5c92bce4ca0e1412b1bd967501e2f6efd086
  * boost-iterator:x64-windows@1.85.0 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-iterator\099bbf852a1d1d8c7f0a7bb7dffb3ae1847b9a93
    boost-json:x64-windows@1.85.0 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-json\b0eb825fbf843ee90e0f2b69aea96c48efdb87b3
  * boost-lexical-cast:x64-windows@1.85.0 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-lexical-cast\1124052a647ffc082af444d1e2713beed81e2172
  * boost-move:x64-windows@1.85.0 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-move\687d6e20922f169fbd9aa2eee51f346523c03880
  * boost-mp11:x64-windows@1.85.0 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-mp11\2bda1e298f7390891b33f230bc83a59045d8e7c8
  * boost-mpl:x64-windows@1.85.0 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-mpl\a72bdbc16d26a9d511485400e527b5a3ef04c027
  * boost-multi-index:x64-windows@1.85.0 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-multi-index\34740bb7b1a6afb63e777c3d8cc80e64b547f09c
  * boost-numeric-conversion:x64-windows@1.85.0 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-numeric-conversion\720ba65f90795653294c5dff7646cd7a6c5fb11b
  * boost-optional:x64-windows@1.85.0 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-optional\0c8968544493922ea8f12a6e6c3782c3b86e7345
  * boost-phoenix:x64-windows@1.85.0 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-phoenix\343d3b0650278b9cf669e787d35e0552e9f0bae7
  * boost-pool:x64-windows@1.85.0 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-pool\e0b197d034800ffc50d4832364fbe8f84faebe62
  * boost-predef:x64-windows@1.85.0 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-predef\0933b332f19fa5eb1373a9f7deeb554eba833786
  * boost-preprocessor:x64-windows@1.85.0 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-preprocessor\584c8e96d2679e4a63162306107e20d79c669677
    boost-program-options:x64-windows@1.85.0 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-program-options\56202533dad3c6ae1eb1d98ef2a966e96ba12d3c
    boost-property-tree:x64-windows@1.85.0 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-property-tree\58cf6bf5d08210849f23756eb9c940265bc3ebaa
  * boost-proto:x64-windows@1.85.0 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-proto\acfd5013ece8c2a3c2f287ccb060487af5b6ef0f
  * boost-range:x64-windows@1.85.0 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-range\4fb92f1ec30f8469609a1d965f1f7dbf0afa54a0
  * boost-ratio:x64-windows@1.85.0 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-ratio\3532faaa9dc0f52aed83c5902761c3883a0df3e1
  * boost-regex:x64-windows@1.85.0 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-regex\18ca23dc0e589aad64e3bf1a63a531c7938d0f53
  * boost-serialization:x64-windows@1.85.0 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-serialization\68c80587bc870f69fb2c3bf8cdf057fe9b2a115c
  * boost-smart-ptr:x64-windows@1.85.0 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-smart-ptr\38581ab402d9d4a6d9c09c62b9b6f3c5b65c816a
  * boost-spirit:x64-windows@1.85.0 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-spirit\34a533fc9c131afc2aab2793ca48ee3ae0b7c620
  * boost-static-assert:x64-windows@1.85.0 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-static-assert\fc871946acae436f469997b7f59604a4e46ee9a5
  * boost-system:x64-windows@1.85.0 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-system\5b85bf9f2f1fe69edf1d99e29470bca45cbeed6b
  * boost-thread:x64-windows@1.85.0 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-thread\8a56e3d5d0b99dcf5df8f2f51f2b8bacfbdabec7
  * boost-throw-exception:x64-windows@1.85.0 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-throw-exception\d1b5ac92ece793a441d7130cbf2721fd544950b7
  * boost-tokenizer:x64-windows@1.85.0 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-tokenizer\d4d77b143e67e2cd1ef8505847a9f23cb9b3faf0
  * boost-tuple:x64-windows@1.85.0 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-tuple\fa6c63977155870de0165ffd7e2c1d921e1d9644
  * boost-type-index:x64-windows@1.85.0 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-type-index\22c535bdcdd75c80dccb28caca98b6da9bf3b890
  * boost-type-traits:x64-windows@1.85.0 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-type-traits\ebc7ae004450bc4a210e8acb1f713a15fc829935
  * boost-typeof:x64-windows@1.85.0 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-typeof\94d6bbcbb519960482696b50301492c2e71a9d30
  * boost-uninstall:x64-windows@1.85.0 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-uninstall\61f71073f29852425b317ad050b3ee54653f924b
  * boost-unordered:x64-windows@1.85.0 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-unordered\46f5ca53ab03102c5ee470de738a5a3404c75235
  * boost-utility:x64-windows@1.85.0 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-utility\a40330e797feb2590aac114545cc70cf636bc5e3
  * boost-variant:x64-windows@1.85.0 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-variant\0fc759f3ec67e2f3f31302d470bd469c5fe0b062
  * boost-variant2:x64-windows@1.85.0 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-variant2\71aeea8a9326c7b978940c83970790090ddcf8f9
  * boost-winapi:x64-windows@1.85.0 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-winapi\ae89b133b4250b5358379d40dda7df98517e6c96
  * vcpkg-boost:x64-windows@2024-04-25 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\vcpkg-boost\885223b657578128c0556fe6b53cfec8cbf50e12
  * vcpkg-cmake:x64-windows@2024-04-18 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\vcpkg-cmake\a10a94e8d0071ed4804d40d0f0f0c5e4e7180afd
  * vcpkg-cmake-config:x64-windows@2022-02-06#1 -- C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\vcpkg-cmake-config\8d54cc4f487d51b655abec5f9c9c3f86ca83311f
Additional packages (*) will be modified to complete this operation.
A suitable version of 7zip was not found (required v23.1.0) Downloading portable 7zip 23.1.0...
Downloading 7zip...
https://github.com/ip7z/7zip/releases/download/23.01/7z2301-extra.7z->C:\git\client-native-host\external\vcpkg\downloads\7z2301-extra.7z
Downloading https://github.com/ip7z/7zip/releases/download/23.01/7z2301-extra.7z
Extracting 7zip...
Restored 0 package(s) from C:\Users\smitten\AppData\Local\vcpkg\archives in 1.06 ms. Use --debug to see more details.
Installing 1/68 vcpkg-cmake-config:x64-windows@2022-02-06#1...
Building vcpkg-cmake-config:x64-windows@2022-02-06#1...
C:\git\client-native-host\external\vcpkg-custom\triplets\x64-windows.cmake: info: loaded overlay triplet from here
C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\vcpkg-cmake-config\8d54cc4f487d51b655abec5f9c9c3f86ca83311f: info: installing overlay port from here
-- Installing: C:/git/client-native-host/external/vcpkg/packages/vcpkg-cmake-config_x64-windows/share/vcpkg-cmake-config/vcpkg_cmake_config_fixup.cmake
-- Installing: C:/git/client-native-host/external/vcpkg/packages/vcpkg-cmake-config_x64-windows/share/vcpkg-cmake-config/vcpkg-port-config.cmake
-- Installing: C:/git/client-native-host/external/vcpkg/packages/vcpkg-cmake-config_x64-windows/share/vcpkg-cmake-config/copyright
-- Performing post-build validation
Stored binaries in 1 destinations in 71.4 ms.
Elapsed time to handle vcpkg-cmake-config:x64-windows: 184 ms
vcpkg-cmake-config:x64-windows package ABI: 1689d46d53ef8d598c54e3d834a4cd5694d92d584f38861f176a4955ada2eca0
Installing 2/68 vcpkg-cmake:x64-windows@2024-04-18...
Building vcpkg-cmake:x64-windows@2024-04-18...
C:\git\client-native-host\external\vcpkg-custom\triplets\x64-windows.cmake: info: loaded overlay triplet from here
C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\vcpkg-cmake\a10a94e8d0071ed4804d40d0f0f0c5e4e7180afd: info: installing overlay port from here
-- Installing: C:/git/client-native-host/external/vcpkg/packages/vcpkg-cmake_x64-windows/share/vcpkg-cmake/vcpkg_cmake_configure.cmake
-- Installing: C:/git/client-native-host/external/vcpkg/packages/vcpkg-cmake_x64-windows/share/vcpkg-cmake/vcpkg_cmake_build.cmake
-- Installing: C:/git/client-native-host/external/vcpkg/packages/vcpkg-cmake_x64-windows/share/vcpkg-cmake/vcpkg_cmake_install.cmake
-- Installing: C:/git/client-native-host/external/vcpkg/packages/vcpkg-cmake_x64-windows/share/vcpkg-cmake/vcpkg-port-config.cmake
-- Installing: C:/git/client-native-host/external/vcpkg/packages/vcpkg-cmake_x64-windows/share/vcpkg-cmake/copyright
-- Performing post-build validation
Stored binaries in 1 destinations in 51.4 ms.
Elapsed time to handle vcpkg-cmake:x64-windows: 190 ms
vcpkg-cmake:x64-windows package ABI: d5130ebdb5c43115ee3089e1bf09cbef617042ddc9c8d7f5e6f4f99762498f26
Installing 3/68 vcpkg-boost:x64-windows@2024-04-25...
Building vcpkg-boost:x64-windows@2024-04-25...
C:\git\client-native-host\external\vcpkg-custom\triplets\x64-windows.cmake: info: loaded overlay triplet from here
C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\vcpkg-boost\885223b657578128c0556fe6b53cfec8cbf50e12: info: installing overlay port from here
-- Installing: C:/git/client-native-host/external/vcpkg/packages/vcpkg-boost_x64-windows/share/vcpkg-boost/usage.in
-- Installing: C:/git/client-native-host/external/vcpkg/packages/vcpkg-boost_x64-windows/share/vcpkg-boost/boost-install.cmake
-- Installing: C:/git/client-native-host/external/vcpkg/packages/vcpkg-boost_x64-windows/share/vcpkg-boost/vcpkg-port-config.cmake
-- Installing: C:/git/client-native-host/external/vcpkg/packages/vcpkg-boost_x64-windows/share/vcpkg-boost/copyright
-- Performing post-build validation
Stored binaries in 1 destinations in 47.8 ms.
Elapsed time to handle vcpkg-boost:x64-windows: 166 ms
vcpkg-boost:x64-windows package ABI: 8a850dee0b49484b3b89484bde47059fb8aeef4e0b9295509e90494201f05179
Installing 4/68 boost-uninstall:x64-windows@1.85.0...
Building boost-uninstall:x64-windows@1.85.0...
C:\git\client-native-host\external\vcpkg-custom\triplets\x64-windows.cmake: info: loaded overlay triplet from here
C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-uninstall\61f71073f29852425b317ad050b3ee54653f924b: info: installing overlay port from here
--
Please use the following command when you need to remove all boost ports/components:
    "./vcpkg remove boost-uninstall:x64-windows --recurse"

-- Performing post-build validation
Stored binaries in 1 destinations in 44.6 ms.
Elapsed time to handle boost-uninstall:x64-windows: 149 ms
boost-uninstall:x64-windows package ABI: c55ebd5b26e28028586042218d56e6600e79e45c53fdabe46cdb197a2a93a3e8
Installing 5/68 boost-cmake:x64-windows@1.85.0...
Building boost-cmake:x64-windows@1.85.0...
C:\git\client-native-host\external\vcpkg-custom\triplets\x64-windows.cmake: info: loaded overlay triplet from here
C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-cmake\bb385ffc8aa74989b8198a777f3181b3a209451a: info: installing overlay port from here
-- Downloading https://github.com/boostorg/boost/archive/boost-1.85.0.tar.gz -> boostorg-boost-boost-1.85.0.tar.gz...
-- Extracting source C:/git/client-native-host/external/vcpkg/downloads/boostorg-boost-boost-1.85.0.tar.gz
-- Using source at C:/git/client-native-host/external/vcpkg/buildtrees/boost-cmake/src/ost-1.85.0-27110fc97f.clean
-- Downloading https://github.com/boostorg/cmake/archive/boost-1.85.0.tar.gz -> boostorg-cmake-boost-1.85.0.tar.gz...
-- Extracting source C:/git/client-native-host/external/vcpkg/downloads/boostorg-cmake-boost-1.85.0.tar.gz
-- Applying patch vcpkg-build.diff
-- Applying patch fix-mpi.diff
-- Applying patch no-prefix.diff
-- Applying patch zstd.diff
-- Applying patch add-optional-deps.diff
-- Applying patch fix-missing-archs.diff
-- Using source at C:/git/client-native-host/external/vcpkg/buildtrees/boost-cmake/src/ost-1.85.0-eff32fc7be.clean
-- Installing: C:/git/client-native-host/external/vcpkg/packages/boost-cmake_x64-windows/share/boost-cmake/usage
-- Found external ninja('1.11.0').
-- Configuring x64-windows
-- Building x64-windows-dbg
-- Building x64-windows-rel
-- Up-to-date: C:/git/client-native-host/external/vcpkg/packages/boost-cmake_x64-windows/share/boost/cmake-build
-- Installing: C:/git/client-native-host/external/vcpkg/packages/boost-cmake_x64-windows/share/boost/cmake-build/BoostFetch.cmake
-- Installing: C:/git/client-native-host/external/vcpkg/packages/boost-cmake_x64-windows/share/boost/cmake-build/BoostInstall.cmake
-- Installing: C:/git/client-native-host/external/vcpkg/packages/boost-cmake_x64-windows/share/boost/cmake-build/BoostMessage.cmake
-- Installing: C:/git/client-native-host/external/vcpkg/packages/boost-cmake_x64-windows/share/boost/cmake-build/BoostRoot.cmake
-- Installing: C:/git/client-native-host/external/vcpkg/packages/boost-cmake_x64-windows/share/boost/cmake-build/BoostTest.cmake
-- Installing: C:/git/client-native-host/external/vcpkg/packages/boost-cmake_x64-windows/share/boost/cmake-build/BoostTestJamfile.cmake
-- Installing: C:/git/client-native-host/external/vcpkg/packages/boost-cmake_x64-windows/share/boost-cmake/vcpkg-port-config.cmake
-- Installing: C:/git/client-native-host/external/vcpkg/packages/boost-cmake_x64-windows/share/boost-cmake/copyright
-- Performing post-build validation
Stored binaries in 1 destinations in 53.9 ms.
Elapsed time to handle boost-cmake:x64-windows: 3.1 s
boost-cmake:x64-windows package ABI: 38d27a6364f4048a9ab0ab67f4df9e973ac2115c6ef301289aeb211eb005a835
Installing 6/68 boost-headers:x64-windows@1.85.0...
Building boost-headers:x64-windows@1.85.0...
C:\git\client-native-host\external\vcpkg-custom\triplets\x64-windows.cmake: info: loaded overlay triplet from here
C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-headers\6cf27bbd161498aef1c033c3b3951b27c6f430b7: info: installing overlay port from here
-- Downloading https://github.com/boostorg/headers/archive/boost-1.85.0.tar.gz -> boostorg-headers-boost-1.85.0.tar.gz...
-- Extracting source C:/git/client-native-host/external/vcpkg/downloads/boostorg-headers-boost-1.85.0.tar.gz
-- Using source at C:/git/client-native-host/external/vcpkg/buildtrees/boost-headers/src/ost-1.85.0-f4cb877742.clean
-- Found external ninja('1.11.0').
-- Configuring x64-windows
-- Building x64-windows-rel
-- Installing: C:/git/client-native-host/external/vcpkg/packages/boost-headers_x64-windows/share/boost-headers/copyright
-- Performing post-build validation
Stored binaries in 1 destinations in 53.3 ms.
Elapsed time to handle boost-headers:x64-windows: 2.2 s
boost-headers:x64-windows package ABI: a2c2b7026cb21f61dbaa1e2fda6223ff060a5bd6d8bc99d2113eb0c378f8e044
Installing 7/68 boost-config:x64-windows@1.85.0...
Building boost-config:x64-windows@1.85.0...
C:\git\client-native-host\external\vcpkg-custom\triplets\x64-windows.cmake: info: loaded overlay triplet from here
C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-config\9c454bf1a50c40d4025fe2ee6edc21720cf39c9e: info: installing overlay port from here
-- Downloading https://github.com/boostorg/config/archive/boost-1.85.0.tar.gz -> boostorg-config-boost-1.85.0.tar.gz...
-- Extracting source C:/git/client-native-host/external/vcpkg/downloads/boostorg-config-boost-1.85.0.tar.gz
-- Using source at C:/git/client-native-host/external/vcpkg/buildtrees/boost-config/src/ost-1.85.0-27fd0e3b2d.clean
-- Found external ninja('1.11.0').
-- Configuring x64-windows
-- Building x64-windows-rel
-- Installing: C:/git/client-native-host/external/vcpkg/packages/boost-config_x64-windows/share/boost-config/copyright
-- Performing post-build validation
Stored binaries in 1 destinations in 270 ms.
Elapsed time to handle boost-config:x64-windows: 4.4 s
boost-config:x64-windows package ABI: eb0afffa9b2d3ced8d496b58ae44f80101ee200ade8fae5b67c5bf07d8ca003d
Installing 8/68 boost-assert:x64-windows@1.85.0...
Building boost-assert:x64-windows@1.85.0...
C:\git\client-native-host\external\vcpkg-custom\triplets\x64-windows.cmake: info: loaded overlay triplet from here
C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-assert\2720690553c459c12a23f54451fe9c9f1d96164c: info: installing overlay port from here
-- Downloading https://github.com/boostorg/assert/archive/boost-1.85.0.tar.gz -> boostorg-assert-boost-1.85.0.tar.gz...
-- Extracting source C:/git/client-native-host/external/vcpkg/downloads/boostorg-assert-boost-1.85.0.tar.gz
-- Using source at C:/git/client-native-host/external/vcpkg/buildtrees/boost-assert/src/ost-1.85.0-3ebeffda26.clean
-- Found external ninja('1.11.0').
-- Configuring x64-windows
-- Building x64-windows-rel
-- Installing: C:/git/client-native-host/external/vcpkg/packages/boost-assert_x64-windows/share/boost-assert/copyright
-- Performing post-build validation
Stored binaries in 1 destinations in 54 ms.
Elapsed time to handle boost-assert:x64-windows: 2.2 s
boost-assert:x64-windows package ABI: b333a190315a1054c68090b59e1a9893ab9a7643cac3bc7dccde34828d948def
Installing 9/68 boost-throw-exception:x64-windows@1.85.0...
Building boost-throw-exception:x64-windows@1.85.0...
C:\git\client-native-host\external\vcpkg-custom\triplets\x64-windows.cmake: info: loaded overlay triplet from here
C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-throw-exception\d1b5ac92ece793a441d7130cbf2721fd544950b7: info: installing overlay port from here
-- Downloading https://github.com/boostorg/throw_exception/archive/boost-1.85.0.tar.gz -> boostorg-throw_exception-boost-1.85.0.tar.gz...
-- Extracting source C:/git/client-native-host/external/vcpkg/downloads/boostorg-throw_exception-boost-1.85.0.tar.gz
-- Using source at C:/git/client-native-host/external/vcpkg/buildtrees/boost-throw-exception/src/ost-1.85.0-86061aa58d.clean
-- Found external ninja('1.11.0').
-- Configuring x64-windows
-- Building x64-windows-rel
-- Installing: C:/git/client-native-host/external/vcpkg/packages/boost-throw-exception_x64-windows/share/boost-throw-exception/copyright
-- Performing post-build validation
Stored binaries in 1 destinations in 53.7 ms.
Elapsed time to handle boost-throw-exception:x64-windows: 2.3 s
boost-throw-exception:x64-windows package ABI: 68f3bcefbbc46cd56b54d30a8d171bee31190c2f73ee8740ea73751b34313eb3
Installing 10/68 boost-predef:x64-windows@1.85.0...
Building boost-predef:x64-windows@1.85.0...
C:\git\client-native-host\external\vcpkg-custom\triplets\x64-windows.cmake: info: loaded overlay triplet from here
C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-predef\0933b332f19fa5eb1373a9f7deeb554eba833786: info: installing overlay port from here
-- Downloading https://github.com/boostorg/predef/archive/boost-1.85.0.tar.gz -> boostorg-predef-boost-1.85.0.tar.gz...
-- Extracting source C:/git/client-native-host/external/vcpkg/downloads/boostorg-predef-boost-1.85.0.tar.gz
-- Using source at C:/git/client-native-host/external/vcpkg/buildtrees/boost-predef/src/ost-1.85.0-5f493b23ed.clean
-- Found external ninja('1.11.0').
-- Configuring x64-windows
-- Building x64-windows-rel
-- Installing: C:/git/client-native-host/external/vcpkg/packages/boost-predef_x64-windows/share/boost-predef/copyright
-- Performing post-build validation
Stored binaries in 1 destinations in 143 ms.
Elapsed time to handle boost-predef:x64-windows: 4.5 s
boost-predef:x64-windows package ABI: 3a92d88cc749bc9b56cb0022db0e90f49492da29bf574885e627607d7d8ec845
Installing 11/68 boost-mp11:x64-windows@1.85.0...
Building boost-mp11:x64-windows@1.85.0...
C:\git\client-native-host\external\vcpkg-custom\triplets\x64-windows.cmake: info: loaded overlay triplet from here
C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-mp11\2bda1e298f7390891b33f230bc83a59045d8e7c8: info: installing overlay port from here
-- Downloading https://github.com/boostorg/mp11/archive/boost-1.85.0.tar.gz -> boostorg-mp11-boost-1.85.0.tar.gz...
-- Extracting source C:/git/client-native-host/external/vcpkg/downloads/boostorg-mp11-boost-1.85.0.tar.gz
-- Using source at C:/git/client-native-host/external/vcpkg/buildtrees/boost-mp11/src/ost-1.85.0-6b8127dc00.clean
-- Found external ninja('1.11.0').
-- Configuring x64-windows
-- Building x64-windows-rel
-- Installing: C:/git/client-native-host/external/vcpkg/packages/boost-mp11_x64-windows/share/boost-mp11/copyright
-- Performing post-build validation
Stored binaries in 1 destinations in 63.9 ms.
Elapsed time to handle boost-mp11:x64-windows: 2.6 s
boost-mp11:x64-windows package ABI: 6d6f54bbc63e8708a56e761d0fd9f4adb5be16f3f2ad08a9250dcd2fc2e22d03
Installing 12/68 boost-static-assert:x64-windows@1.85.0...
Building boost-static-assert:x64-windows@1.85.0...
C:\git\client-native-host\external\vcpkg-custom\triplets\x64-windows.cmake: info: loaded overlay triplet from here
C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-static-assert\fc871946acae436f469997b7f59604a4e46ee9a5: info: installing overlay port from here
-- Downloading https://github.com/boostorg/static_assert/archive/boost-1.85.0.tar.gz -> boostorg-static_assert-boost-1.85.0.tar.gz...
-- Extracting source C:/git/client-native-host/external/vcpkg/downloads/boostorg-static_assert-boost-1.85.0.tar.gz
-- Using source at C:/git/client-native-host/external/vcpkg/buildtrees/boost-static-assert/src/ost-1.85.0-32286774bc.clean
-- Found external ninja('1.11.0').
-- Configuring x64-windows
-- Building x64-windows-rel
-- Installing: C:/git/client-native-host/external/vcpkg/packages/boost-static-assert_x64-windows/share/boost-static-assert/copyright
-- Performing post-build validation
Stored binaries in 1 destinations in 51.8 ms.
Elapsed time to handle boost-static-assert:x64-windows: 2.2 s
boost-static-assert:x64-windows package ABI: 04de345acfe51d82b96c47c375c1bf0aef716f4519ba4aaff379966e1edbab5c
Installing 13/68 boost-core:x64-windows@1.85.0...
Building boost-core:x64-windows@1.85.0...
C:\git\client-native-host\external\vcpkg-custom\triplets\x64-windows.cmake: info: loaded overlay triplet from here
C:\git\client-native-host\external\vcpkg\buildtrees\versioning_\versions\boost-core\195375664be82cbc16178de90096e451de070d80: info: installing overlay port from here
-- Downloading https://github.com/boostorg/core/archive/boost-1.85.0.tar.gz -> boostorg-core-boost-1.85.0.tar.gz...
[DEBUG] To include the environment variables in debug output, pass --debug-env
[DEBUG] Trying to load bundleconfig from C:\git\client-native-host\external\vcpkg\vcpkg-bundle.json
[DEBUG] Failed to open: C:\git\client-native-host\external\vcpkg\vcpkg-bundle.json
[DEBUG] Bundle config: readonly=false, usegitregistry=false, embeddedsha=nullopt, deployment=Git, vsversion=nullopt
[DEBUG] Metrics enabled.
[DEBUG] Feature flag 'binarycaching' unset
[DEBUG] Feature flag 'compilertracking' unset
[DEBUG] Feature flag 'registries' unset
[DEBUG] Feature flag 'versions' unset
[DEBUG] Feature flag 'dependencygraph' unset
Downloading https://github.com/boostorg/core/archive/boost-1.85.0.tar.gz
[DEBUG] Trying to hash C:\git\client-native-host\external\vcpkg\downloads\boostorg-core-boost-1.85.0.tar.gz.17532.part
[DEBUG] C:\git\client-native-host\external\vcpkg\downloads\boostorg-core-boost-1.85.0.tar.gz.17532.part has hash a1e774c98b537dd42018742af68f5889af1afd4e6c9809399987124e56a3b9ae2f20e8173170bc6fc0ad76fb95e2da7b9d385a4037e9ee12011fc02bf8f7e009
error: Failed to download from mirror set
error: File does not have the expected hash:
url: https://github.com/boostorg/core/archive/boost-1.85.0.tar.gz
File: C:\git\client-native-host\external\vcpkg\downloads\boostorg-core-boost-1.85.0.tar.gz.17532.part
Expected hash: 3a7be75e52f5c20830fccb9e7391a1e4556ebb072e6324df95b1ba38bed46e24f4c9f27a62a1099eddc90f2ac1ede083f0c850e2dc27fd42375d028516f675b3
Actual hash: a1e774c98b537dd42018742af68f5889af1afd4e6c9809399987124e56a3b9ae2f20e8173170bc6fc0ad76fb95e2da7b9d385a4037e9ee12011fc02bf8f7e009
[DEBUG] D:\a\_work\1\s\src\vcpkg\base\downloads.cpp(997):
[DEBUG] Time in subprocesses: 0us
[DEBUG] Time in parsing JSON: 8us
[DEBUG] Time in JSON reader: 0us
[DEBUG] Time in filesystem: 1664us
[DEBUG] Time in loading ports: 0us
[DEBUG] Exiting after 382 ms (361523us)

CMake Error at scripts/cmake/vcpkg_download_distfile.cmake:32 (message):

      Failed to download file with error: 1
      If you are using a proxy, please check your proxy setting. Possible causes are:

      1. You are actually using an HTTP proxy, but setting HTTPS_PROXY variable
         to `https://address:port`. This is not correct, because `https://` prefix
         claims the proxy is an HTTPS proxy, while your proxy (v2ray, shadowsocksr
         , etc..) is an HTTP proxy. Try setting `http://address:port` to both
         HTTP_PROXY and HTTPS_PROXY instead.

      2. If you are using Windows, vcpkg will automatically use your Windows IE Proxy Settings
         set by your proxy software. See https://github.com/microsoft/vcpkg-tool/pull/77
         The value set by your proxy might be wrong, or have same `https://` prefix issue.

      3. Your proxy's remote server is out of service.

      If you've tried directly download the link, and believe this is not a temporary
      download server failure, please submit an issue at https://github.com/Microsoft/vcpkg/issues
      to report this upstream download server failure.

Call Stack (most recent call first):
  scripts/cmake/vcpkg_download_distfile.cmake:270 (z_vcpkg_download_distfile_show_proxy_and_fail)
  scripts/cmake/vcpkg_from_github.cmake:106 (vcpkg_download_distfile)
  buildtrees/versioning_/versions/boost-core/195375664be82cbc16178de90096e451de070d80/portfile.cmake:3 (vcpkg_from_github)
  scripts/ports.cmake:175 (include)

error: building boost-core:x64-windows failed with: BUILD_FAILED
Elapsed time to handle boost-core:x64-windows: 506 ms
Please ensure you're using the latest port files with `git pull` and `vcpkg update`.
Then check for known issues at:
  https://github.com/microsoft/vcpkg/issues?q=is%3Aissue+is%3Aopen+in%3Atitle+boost-core
You can submit a new issue at:
  https://github.com/microsoft/vcpkg/issues/new?title=[boost-core]+Build+error+on+x64-windows&body=Copy+issue+body+from+C%3A%2Fgit%2Fclient-native-host%2Fexternal%2Fvcpkg%2Finstalled-x64-windows%2Fvcpkg%2Fissue_body.md
You can also submit an issue by running (GitHub CLI must be installed):
  gh issue create -R microsoft/vcpkg --title "[boost-core] Build failure on x64-windows" --body-file C:/git/client-native-host/external/vcpkg/installed-x64-windows/vcpkg/issue_body.md
-- Running vcpkg install - failed
CMake Error at external/vcpkg/scripts/buildsystems/vcpkg.cmake:899 (message):
  vcpkg install failed.  See logs for more information:
  C:\git\client-native-host\build\win-x64-debug\vcpkg-manifest-install.log
Call Stack (most recent call first):
  dev/make/projectInit/toolchain.cmake:32 (include)
  C:/Program Files/CMake/share/cmake-3.27/Modules/CMakeDetermineSystem.cmake:148 (include)
  CMakeLists.txt:20 (project)

CMake Error: CMake was unable to find a build program corresponding to "Ninja".  CMAKE_MAKE_PROGRAM is not set.  You probably need to select a different build tool.
-- Configuring incomplete, errors occurred!

### Additional context

_No response_

Note that if I use commit hash a8954b904ad2a6939ecd8fc213e87702fa1243ea, I don't encounter this build error. That commit's message is entitled "fix hashes" so maybe a new release is needed that includes this fix?

No. vcpkg releases are purely time-based.

Fixed in #38979

authors: DSMitten WangWeiLin-MV dg0yt


text:
[New Port Request] < EventBus >

Library name
EventBus
Library description
A lightweight and very fast event bus / event framework for C++17
Source repository URL
https://github.com/gelldur/EventBus
Project homepage (if different from the source repository)
No response
Anything else that is useful to know when adding (such as optional features the library may have that should be included)
No response

@ilongshan This library uses an older version of catch2 and since overrides are not active in the script mode, I am unsure, how is that handled here?

@motazmuhammad Not sure how to deal with it. Maybe pending the port util the project updates to the catch2 v3.

Is catch2 needed for something else than tests?
vcpkg port shall not run tests. So any catch2 dependency can be disabled.

@dg0yt , just for tests thank you, removing it does solve the problem,
another question in that area , it seems that the .lib files are not generated in the dynamic build, which causes this error
LINK : fatal error LNK1104: cannot open file 'lib\EventBusd.lib'
the dll files are existent however, this is a problem with dynamic linking only as if I set the linkage to static only the build works fine, the only way I can think of to solve this problem is via adding a patch to cmakelists file to force it to produce lib files, have you faced that before? or do you know how it should be solved? or should I make this library static only library?

If there is a DLL (for runtime) without lib (for build time), then the packages lacks proper exports for Windows. Then do not build a DLL. Start the portfile with:
if(VCPKG_TARGET_IS_WINDOWS)
    vcpkg_check_linkage(ONLY_STATIC_LIBRARY)
endif()

@dg0yt thank you, I will use that then

authors: dg0yt ilongshan motazmuhammad


text:
[vcpkg] Add a schema file for vcpkg.json

This is related to #12175 .
This is absolutely not as tested as it should be, but I'm not sure how to go about it. I gess some set of known valid and known invalid manifest files would be required.
I choose the path an filename fairly arbitrarily, feel free to move it around.

Also, if that path ends up being the final one, an id field should be added with and url providing the schema, either the github raw one, or something else:
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "$id: "https://raw.githubusercontent.com/microsoft/vcpkg/master/scripts/vcpkg.schema.json",
  // ...
}

I think that this is really good, but can you make the identifiers for the definitions match the spec? platformExpression -> platform-expression?

I wondered wether too do that or use the conventional json casing. I'll change the case when I have some time

done, all definitions are now with-dashes. I kept description as description-field to avoid mixing it up with the description keyword

@Edhebi did you intend to mark this as ready to merge instead of a draft?

@ras0219 oops, my bad. I'll mark it as ready to merge

Thanks so much @Edhebi!

authors: Edhebi ras0219 strega-nil


text:
Change Nuget binary cache pre-release info to always start with letters

Describe the pull request

What does your PR fix? Fixes #14542

Which triplets are supported/not supported? Have you updated the CI baseline? Not applicable, this PR affects the "tool" vcpkg.exe

Does your PR follow the maintainer guide? Yes. I ran the full test suite and everything passes.

cc @ras0219

The failing check is for port sophus, and the error is :
ninja: error: 'D:/installed/x64-windows-static/debug/lib/openblas.lib', needed by 'test/ceres/test_ceres_se3.exe', missing and no known rule to make it

which is not related to my PR. Is it possible that it was already broken?

Thanks for your contribution!

authors: BillyONeal JackBoosY frivard-coveo


text:
[comms] update comms libs to latest version

Describe the pull request
\cc https://github.com/commschamp/comms_champion/issues/13

What does your PR fix?
updates comms to latest

Which triplets are supported/not supported? Have you updated the CI baseline? uwp/ yes

Does your PR follow the maintainer guide? yes

Thanks!

authors: BillyONeal mathisloge


text:
[vcpkg script] Ios support for meson and autotools based ports

Describe the pull request

What does your PR fix?

Improves ios support for autotools and meson based ports
Supersedes https://github.com/microsoft/vcpkg/pull/25201 by taking the same approach as for meson by picking up VCPKG_DETECTED_CMAKE_OSX_SYSROOT
~Depends on https://github.com/microsoft/vcpkg/pull/25009 to be fully functional~

Which triplets are supported/not supported? Have you updated the CI baseline?
all

Does your PR follow the maintainer guide?
Yes

If you have added/updated a port: Have you run ./vcpkg x-add-version --all and committed the result?
Yes

This no longer depends on a different pr
@LilyWangLL @JackBoosY

@JackBoosY this is not dependent on a different PR, #26564 fixes an unrelated issue that surfaced here for reasons beyond my understanding.
On the other hand, https://github.com/microsoft/vcpkg/pull/26520 conflicts with this PR and the two approaches should be compared in order to proceed to approval and merge.

https://github.com/microsoft/vcpkg/pull/26564 fixes an unrelated issue that surfaced here for reasons beyond my understanding.

It means we need to wait for #26564 merge first.

#26520 (and possibly any world-rebuild) is in the exactly same situation and received an "approval" instead of "depends:different-pr" today.

Furthermore, there are other osx build issues on both pull requests, which would ideally only be solved by one, not two persons in parallel, hence some coordination between the two approaches by maintainers would be good, even in parallel of a PR that needs merging.

@BillyONeal Do you have any ideas that which PR should we pick between this PR and #26520?

@BillyONeal Do you have any ideas that which PR should we pick between this PR and #26520?

Unfortunately I know very little about autotools or meson or iOS so I don't really feel qualified to add much here.

Waiting for merge https://github.com/microsoft/vcpkg/pull/26646/  and https://github.com/microsoft/vcpkg/pull/26687

Potentially superseded by https://github.com/microsoft/vcpkg/pull/26617

Ping @m-kuhn for response. Is work still being done for this PR? Could you please resolve the conflicts?

This has been superseded by https://github.com/microsoft/vcpkg/pull/26617 and others

authors: BillyONeal JackBoosY LilyWangLL m-kuhn


text:
[vcpkg baseline][nghttp3] Fix configure when cunit was installed

When CUnit was installed and found, nghttp3 will enable static build:
...
if(HAVE_CUNIT OR ENABLE_STATIC_LIB)
  # Static library (for unittests because of symbol visibility)
  add_library(nghttp3_static STATIC ${nghttp3_SOURCES})
...

Fix this and disable testing.
Related: https://dev.azure.com/vcpkg/public/_build/results?buildId=77177&view=results&j=878666d5-db33-5b27-9e7d-b0c7ee352005

Thanks!

authors: JackBoosY JavierMatosD


text:
[ZArchive] Add new port

Describe the pull request

What does your PR do?
Adds ZArchive port

Which triplets are supported/not supported? Have you updated the CI baseline?
N/A, No

Does your PR follow the maintainer guide?
Yes

If you have added/updated a port: Have you run ./vcpkg x-add-version --all and committed the result?
Yes

A new version needs to be released to fix the build issues (Exzap/ZArchive#11).

@Zopolis4, Thanks for your pr, Please get failure logs here. Please ping me if you need any help.

Pinging @Zopolis4 for response. Is work still being done for this PR?

No.

I don't want any messages..no
On Tue, 11 Oct, 2022, 12:39 Maximilian Downey Twiss, <
@.***> wrote:

No.
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vcpkg/pull/26694#issuecomment-1274187988,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APWGHBP6PXPWNQAMI42GWHLWCUHCDANCNFSM6AAAAAAQFLGGCU
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


text:
[benchmark] Fix release tag

Fixes #6681

duplicate of #6675

Someone beat me to the punch

authors: Neumann-A jumpinjackie


text:
Refactor GitHub steps into an Azure Wizard

Fixes https://github.com/microsoft/vscode-azureappservice/issues/764

I'm going to continue making changes to this since it'll be necessary for another PR. It shouldn't be anything huge, just passing in the name of org/repo like we talked about offline.

Never mind, Matt didn't like the automatically getting org/repo so not gonna add more to this PR.

repo: microsoft/vscode-azuretools