Build Failed Building Package bzip2

Question

Build Failed Building Package bzip2

Kennedy747 opened this issue 3 years ago · 8 comments

OS & System:
Windows 10 Home with gpedit.msc GUI unlocked
AMD Ryzen 7 5800X, with GTX 3080

To produce:
I ran vcpkg.exe to install all libarries (ie: vcpkg.exe install --triplet x64-windows libusb eigen3 boost opencv glfw3 glew gtest dirent)

What expected:
I expected it not to fail

Note I also do not have a proxy installed.

  Failed to download file.
  If you use a proxy, please set the HTTPS_PROXY and HTTP_PROXY environment
  variables to "https://user:password@your-proxy-ip-address:port/".
  Otherwise, please submit an issue at https://github.com/Microsoft/vcpkg/issues

Call Stack (most recent call first):
scripts/cmake/vcpkg_acquire_msys.cmake:89 (vcpkg_download_distfile)
scripts/cmake/vcpkg_acquire_msys.cmake:137 (msys_package_download)
scripts/cmake/vcpkg_find_acquire_program.cmake:427 (vcpkg_acquire_msys)
scripts/cmake/vcpkg_fixup_pkgconfig.cmake:271 (vcpkg_find_acquire_program)
ports/bzip2/portfile.cmake:43 (vcpkg_fixup_pkgconfig)
scripts/ports.cmake:135 (include)

Error: Building package bzip2:x64-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: bzip2:x64-windows
Vcpkg version: 2020.06.15-nohash

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

Answer 1 · 2022-04-16T06:43:51.000Z

Package: bzip2:x64-windows
Vcpkg version: 2020.06.15-nohash

goto(2022);

Answer 2 · 2022-04-16T06:58:07.000Z

Package: bzip2:x64-windows
Vcpkg version: 2020.06.15-nohash
goto(2022);

I'm trying to install and compile the Prophesee OpenEb and it says in the installation guild to specifically use that version. https://docs.prophesee.ai/stable/installation/windows_open_from_source.html

Answer 3 · 2022-04-16T08:10:44.000Z

This issue with 2020.11-1 cannot be fixed in 2022.

Apart from all the resolved issues since 2020 (including security fixes by upstreams), the key problem is that for ports based on autotools, vcpkg relies on MSYS2 tool binaries which are available at the time of the vcpkg commit but not forever. MSYS2 is a rolling release project, and outdated binary packages are removed after some months.

The only mitigation is using manifest mode, for combining the latest vcpkg scripts (MSYS2 downloads) with selected versions of desired ports.

Answer 4 · 2022-04-16T08:15:14.000Z

I'm trying to install and compile the Prophesee OpenEb and it says in the installation guild to specifically use that version. https://docs.prophesee.ai/stable/installation/windows_open_from_source.html

FTR this instructions also provide modification to the relevant script, but it might be oudated as well. I assume you already tried that.

Answer 5 · 2022-04-19T21:41:30.000Z

We just got hit by this. When CI starts failing one week with no other changes, this is bad news.

Answer 6 · 2022-04-20T05:52:43.000Z

@MichaelGoulding You are building Prophesee OpenEb and started from scratch? Or you didn't save external downloads?

Answer 7 · 2022-05-07T06:16:20.000Z

@Kennedy747 Does this issue has new updates?

Answer 8 · 2022-05-16T08:18:09.000Z

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