microsoft / vcpkg

C++ Library Manager for Windows, Linux, and MacOS
MIT License
22.8k stars 6.3k forks source link

[aom] Build error #33059

Closed Sam960312 closed 8 months ago

Sam960312 commented 1 year ago

Package: libvpx[core]:x64-windows-static -> 1.12.0#1

Host Environment

To Reproduce

vcpkg install libvpx:x64-windows-static libyuv:x64-windows-static opus:x64-windows-static

Failure logs

-- Using cached webmproject-libvpx-v1.12.0.tar.gz.
-- Cleaning sources at D:/runoob-greeting/rustdesk/vcpkg/buildtrees/libvpx/src/v1.12.0-2729413caf.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source D:/runoob-greeting/rustdesk/vcpkg/downloads/webmproject-libvpx-v1.12.0.tar.gz
-- Applying patch 0002-Fix-nasm-debug-format-flag.patch
-- Applying patch 0003-add-uwp-v142-and-v143-support.patch
-- Applying patch 0004-remove-library-suffixes.patch
-- Using source at D:/runoob-greeting/rustdesk/vcpkg/buildtrees/libvpx/src/v1.12.0-2729413caf.clean
-- 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.
-- Downloading https://repo.msys2.org/msys/x86_64/grep-3.0-2-x86_64.pkg.tar.xz;https://www2.futureware.at/~nickoe/msys2-mirror/msys/x86_64/grep-3.0-2-x86_64.pkg.tar.xz;https://mirror.yandex.ru/mirrors/msys2/msys/x86_64/grep-3.0-2-x86_64.pkg.tar.xz;https://mirrors.tuna.tsinghua.edu.cn/msys2/msys/x86_64/grep-3.0-2-x86_64.pkg.tar.xz;https://mirrors.ustc.edu.cn/msys2/msys/x86_64/grep-3.0-2-x86_64.pkg.tar.xz;https://mirror.bit.edu.cn/msys2/msys/x86_64/grep-3.0-2-x86_64.pkg.tar.xz;https://mirror.selfnet.de/msys2/msys/x86_64/grep-3.0-2-x86_64.pkg.tar.xz;https://mirrors.sjtug.sjtu.edu.cn/msys2/msys/x86_64/grep-3.0-2-x86_64.pkg.tar.xz -> msys-grep-3.0-2-x86_64.pkg.tar.xz...
[DEBUG] To include the environment variables in debug output, pass --debug-env
[DEBUG] Trying to load bundleconfig from D:\runoob-greeting\rustdesk\vcpkg\vcpkg-bundle.json
[DEBUG] Failed to open: D:\runoob-greeting\rustdesk\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
Downloading https://repo.msys2.org/msys/x86_64/grep-3.0-2-x86_64.pkg.tar.xz
Downloading https://www2.futureware.at/~nickoe/msys2-mirror/msys/x86_64/grep-3.0-2-x86_64.pkg.tar.xz
Downloading https://mirror.yandex.ru/mirrors/msys2/msys/x86_64/grep-3.0-2-x86_64.pkg.tar.xz
Downloading https://mirrors.tuna.tsinghua.edu.cn/msys2/msys/x86_64/grep-3.0-2-x86_64.pkg.tar.xz
Downloading https://mirrors.ustc.edu.cn/msys2/msys/x86_64/grep-3.0-2-x86_64.pkg.tar.xz
Downloading https://mirror.bit.edu.cn/msys2/msys/x86_64/grep-3.0-2-x86_64.pkg.tar.xz
warning: Download failed -- retrying after 1000ms
warning: Download failed -- retrying after 2000ms
warning: Download failed -- retrying after 4000ms
Downloading https://mirror.selfnet.de/msys2/msys/x86_64/grep-3.0-2-x86_64.pkg.tar.xz
Downloading https://mirrors.sjtug.sjtu.edu.cn/msys2/msys/x86_64/grep-3.0-2-x86_64.pkg.tar.xz
error: Failed to download from mirror set
error: https://repo.msys2.org/msys/x86_64/grep-3.0-2-x86_64.pkg.tar.xz: failed: status code 404
error: https://www2.futureware.at/~nickoe/msys2-mirror/msys/x86_64/grep-3.0-2-x86_64.pkg.tar.xz: failed: status code 404
error: https://mirror.yandex.ru/mirrors/msys2/msys/x86_64/grep-3.0-2-x86_64.pkg.tar.xz: failed: status code 404
error: https://mirrors.tuna.tsinghua.edu.cn/msys2/msys/x86_64/grep-3.0-2-x86_64.pkg.tar.xz: failed: status code 404
error: https://mirrors.ustc.edu.cn/msys2/msys/x86_64/grep-3.0-2-x86_64.pkg.tar.xz: failed: status code 404
error: https://mirror.bit.edu.cn/msys2/msys/x86_64/grep-3.0-2-x86_64.pkg.tar.xz: WinHttpSendRequest failed with exit code 12002
error: https://mirror.bit.edu.cn/msys2/msys/x86_64/grep-3.0-2-x86_64.pkg.tar.xz: WinHttpSendRequest failed with exit code 12002
error: https://mirror.bit.edu.cn/msys2/msys/x86_64/grep-3.0-2-x86_64.pkg.tar.xz: WinHttpSendRequest failed with exit code 12002
error: https://mirror.bit.edu.cn/msys2/msys/x86_64/grep-3.0-2-x86_64.pkg.tar.xz: WinHttpSendRequest failed with exit code 12002
error: https://mirror.selfnet.de/msys2/msys/x86_64/grep-3.0-2-x86_64.pkg.tar.xz: failed: status code 404
error: https://mirrors.sjtug.sjtu.edu.cn/msys2/msys/x86_64/grep-3.0-2-x86_64.pkg.tar.xz: failed: status code 404
[DEBUG] D:\a\_work\1\s\src\vcpkg\base\downloads.cpp(961): 
[DEBUG] Time in subprocesses: 0us
[DEBUG] Time in parsing JSON: 21us
[DEBUG] Time in JSON reader: 0us
[DEBUG] Time in filesystem: 12517us
[DEBUG] Time in loading ports: 0us
[DEBUG] Exiting after 2.7 min (160838607us)

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:216 (z_vcpkg_acquire_msys_declare_package)
  ports/libvpx/portfile.cmake:22 (vcpkg_acquire_msys)
  scripts/ports.cmake:147 (include)

Additional context

github-actions[bot] commented 1 year ago

Try updating your vcpkg version via git pull to resolve this issue. MSYS2 downloads are removed from the upstream servers from time to time, so using an up-to-date vcpkg version is necessary.

Sam960312 commented 1 year ago

Yes, I have tried, and it still reports this wrong. "PS D:\runoob-greeting\rustdesk> vcpkg update Using local portfile versions. To update the local portfiles, use git pull. No packages need updating."

dg0yt commented 1 year ago

For git pull, you need to be on the master branch, not on some historical git tag.

Sam960312 commented 1 year ago

My local branch is on the master. pls check help me. Thanks.

Sam960312 commented 1 year ago

Administrator@WIN10_071 MINGW64 /d/runoob-greeting/rustdesk (master) $ git pull Already up to date.

Administrator@WIN10_071 MINGW64 /d/runoob-greeting/rustdesk (master) $

Sam960312 commented 1 year ago

PS D:\runoob-greeting\rustdesk> git checkout master Already on 'master' Your branch is up to date with 'origin/master'. PS D:\runoob-greeting\rustdesk>

dg0yt commented 1 year ago

vcpkg-tool version: 2023-04-07-bedcba5172f5e4b91caac660ab7afe92c27a9895 vcpkg-scripts version: 501db0f 2023-04-15 (4 months ago)

This isn't our head of master. Do you use a fork?

Sam960312 commented 1 year ago

I am compiling rustDesk and it told me to do so. Is there any problem? https://rustdesk.com/docs/zh-cn/dev/build/windows/

dg0yt commented 1 year ago

So they tell you to checkout 2023.04.15. Obviously, this will miss all fixes made since this tag, and it can't receive any further fixes. AFAIU these tags only exist because people would use even older tags otherwise. If you want to pin package versions, use manifest mode.

Sam960312 commented 1 year ago

Thank you for your support. I will give it a try as you suggested.

Sam960312 commented 1 year ago

Hi, there are always errors during the download process, do I need to build a ladder to get it?

error: Failed to download from mirror set error: https://github.com/PowerShell/PowerShell/releases/download/v7.2.11/PowerShell-7.2.11-win-x86.zip: WinHttpReadData failed with exit code 12002 error: https://github.com/PowerShell/PowerShell/releases/download/v7.2.11/PowerShell-7.2.11-win-x86.zip: WinHttpReadData failed with exit code 12002 error: https://github.com/PowerShell/PowerShell/releases/download/v7.2.11/PowerShell-7.2.11-win-x86.zip: WinHttpReadData failed with exit code 12002 error: https://github.com/PowerShell/PowerShell/releases/download/v7.2.11/PowerShell-7.2.11-win-x86.zip: WinHttpReadData failed with exit code 12002

dg0yt commented 1 year ago

The download works for me. Given https://github.com/microsoft/vcpkg/issues/33061, I would guess that you network provider is the problem.

Sam960312 commented 1 year ago

Okay.

github-actions[bot] commented 1 year ago

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.

github-actions[bot] commented 11 months ago

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.

github-actions[bot] commented 10 months ago

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.

Adela0814 commented 8 months ago

We hope your question was answered to your satisfaction; if it wasn't, you can reopen with more info.