Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[icu]Build error #30563

Closed
larixsoft opened this issue Mar 31, 2023 · 5 comments
Closed

[icu]Build error #30563

larixsoft opened this issue Mar 31, 2023 · 5 comments
Assignees
@JonLiu1993
Labels
category:tool-update The issue is with build tool or build script, which requires update or should be executed correctly

Comments

@larixsoft
Copy link

Host Environment

  • OS: [Windows]
  • Compiler: vs2019

To Reproduce

Steps to reproduce the behavior:

vcpkg install qtbase

Failure logs

C:\vcpkg>vcpkg.exe install qtbase
warning: Starting with the September 2023 release, the default triplet for vcpkg libraries will change from x86-windows to the detected host triplet (x64-windows). To resolve this message, add --triplet x86-windows to keep the same behavior.
Computing installation plan...
The following packages will be built and installed:

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_acquire_msys.cmake:26 (vcpkg_download_distfile)
scripts/cmake/vcpkg_acquire_msys.cmake:67 (z_vcpkg_acquire_msys_download_package)
scripts/cmake/vcpkg_acquire_msys.cmake:345 (z_vcpkg_acquire_msys_declare_package)
scripts/cmake/vcpkg_configure_make.cmake:224 (vcpkg_acquire_msys)
ports/icu/portfile.cmake:55 (vcpkg_configure_make)
scripts/ports.cmake:147 (include)

error: building icu:x64-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+icu
You can submit a new issue at:
https://github.com/microsoft/vcpkg/issues/new?template=report-package-build-failure.md&title=[icu]+Build+error
Include '[icu] 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-02-16-12e657924d99511514c0287ca5ce46882d3657c7
vcpkg-scripts version: 5b12143 2023-03-30 (6 hours ago)
@larixsoft larixsoft added the category:port-bug The issue is with a library, which is something the port should already support label Mar 31, 2023
@JonLiu1993 JonLiu1993 self-assigned this Mar 31, 2023
@kotori2
Copy link
Contributor

kotori2 commented Mar 31, 2023

I got this issue as well. It seems that MSYS is deleting old ports. Is there any archive for them?

@kotori2 kotori2 mentioned this issue Mar 31, 2023
Closed
@ctapmex
Copy link

ctapmex commented Mar 31, 2023

Updating the msys version is a patching of current problems. The problem is deeper.
I caught a similar error when trying to rebuild a project that hasn't changed in a year. It turns out that using vcpkg I cannot guarantee the possibility of rebuilding in a month / year.
The solution to the problem is that vcpkg must download dependencies from its own mirror, on which files are stored for a long time.

@JonLiu1993 JonLiu1993 added category:tool-update The issue is with build tool or build script, which requires update or should be executed correctly and removed category:port-bug The issue is with a library, which is something the port should already support labels Mar 31, 2023
@JonLiu1993
Copy link
Member

Duplicate of #30542

@JonLiu1993 JonLiu1993 marked this as a duplicate of #30542 Mar 31, 2023
@JonLiu1993 JonLiu1993 closed this as not planned Won't fix, can't repro, duplicate, stale Mar 31, 2023
@yanggaome
Copy link

@JonLiu1993 is this going to be fixed? our pipeline (MSFT internal) is failing due to this

@JonLiu1993
Copy link
Member

@yanggaome, This issue is fixed by PR #30546, please rerun your pipeline.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@JonLiu1993 JonLiu1993

Labels
category:tool-update The issue is with build tool or build script, which requires update or should be executed correctly
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[msys] update msys-runtime kotori2/vcpkg
5 participants
@ctapmex @yanggaome @larixsoft @kotori2 @JonLiu1993