vcpkg
vcpkg copied to clipboard
[freexl] Build error on x64-windows
Package: freexl:[email protected]
Host Environment
- Host: x64-windows
- Compiler: MSVC 19.38.33134.0
- vcpkg-tool version: 2024-04-23-d6945642ee5c3076addd1a42c331bbf4cfc97457 vcpkg-scripts version: c4467cb68 2024-06-21 (4 days ago)
To Reproduce
vcpkg install osg:x64-windows --recurse
Failure logs
-- Downloading https://www.gaia-gis.it/gaia-sins/freexl-sources/freexl-2.0.0.tar.gz -> freexl-2.0.0.tar.gz...
[DEBUG] To include the environment variables in debug output, pass --debug-env
[DEBUG] Trying to load bundleconfig from E:\vcpkg\vcpkg-bundle.json
[DEBUG] Failed to open: E:\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://www.gaia-gis.it/gaia-sins/freexl-sources/freexl-2.0.0.tar.gz
warning: Download failed -- retrying after 1000ms
warning: Download failed -- retrying after 2000ms
[DEBUG] Trying to hash E:\vcpkg\downloads\freexl-2.0.0.tar.gz.5360.part
[DEBUG] E:\vcpkg\downloads\freexl-2.0.0.tar.gz.5360.part has hash 446150e87d83e3a0d154c6c12d87b650586a6a517c3c548dfebebc56891ffb4a434761b9aaf859c9f69539f06dfb867ae3ad5f410d56dd4955c7f29a19e247d9
error: Failed to download from mirror set
error: https://www.gaia-gis.it/gaia-sins/freexl-sources/freexl-2.0.0.tar.gz: WinHttpReadData failed with exit code 12002
error: https://www.gaia-gis.it/gaia-sins/freexl-sources/freexl-2.0.0.tar.gz: WinHttpReadData failed with exit code 12002
error: File does not have the expected hash:
url: https://www.gaia-gis.it/gaia-sins/freexl-sources/freexl-2.0.0.tar.gz
File: E:\vcpkg\downloads\freexl-2.0.0.tar.gz.5360.part
Expected hash: 663ccc321c2f0dcab8ad9255b2a77066c2046d531a0aa723fb114301fa27b53bf980787dd2548c46541036eceef988c5eedf2bec053adf628929470e67ddc17a
Actual hash: 446150e87d83e3a0d154c6c12d87b650586a6a517c3c548dfebebc56891ffb4a434761b9aaf859c9f69539f06dfb867ae3ad5f410d56dd4955c7f29a19e247d9
[DEBUG] D:\a\_work\1\s\src\vcpkg\base\downloads.cpp(997):
[DEBUG] Time in subprocesses: 0us
[DEBUG] Time in parsing JSON: 5us
[DEBUG] Time in JSON reader: 0us
[DEBUG] Time in filesystem: 943us
[DEBUG] Time in loading ports: 0us
[DEBUG] Exiting after 13 min (756141989us)
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)
ports/freexl/portfile.cmake:1 (vcpkg_download_distfile)
scripts/ports.cmake:191 (include)
I can't repro this issue, I can install freexl succeed on the latest vcpkg. Did you change the files of freexl?
This is an automated message. Per our repo policy, stale issues get closed if there has been no activity in the past 28 days. The issue will be automatically closed in 14 days. If you wish to keep this issue open, please add a new comment.
We haven't been able to repro this; if more information comes up, or this issue appears again, please reopen.