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.

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

[libavif] Build failure dependency libyuv not found #44276

Open
MarnixKuijs opened this issue Mar 9, 2025 · 4 comments
Open

[libavif] Build failure dependency libyuv not found #44276

MarnixKuijs opened this issue Mar 9, 2025 · 4 comments
Assignees
Labels
requires:repro The issue is not currently repro-able

Comments

@MarnixKuijs
Copy link

MarnixKuijs commented Mar 9, 2025

Operating system

Windows

Compiler

MSVC

Steps to reproduce the behavior

vcpkg install libavif

Failure logs

Computing installation plan...
The following packages will be built and installed:
    libavif:x64-windows@1.1.1#1
  * libjpeg-turbo:x64-windows@3.1.0#1
  * libyuv:x64-windows@1896#1
  * vcpkg-cmake:x64-windows@2024-04-23
  * vcpkg-cmake-config:x64-windows@2024-05-23
  * vcpkg-cmake-get-vars:x64-windows@2024-09-22
Additional packages (*) will be modified to complete this operation.
Detecting compiler hash for triplet x64-windows...
Compiler found: C:/Program Files/Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.43.34808/bin/Hostx64/x64/cl.exe
Restored 5 package(s) from D:\Dev\Repos\Vcpkg\cache in 86.9 ms. Use --debug to see more details.
Installing 1/6 vcpkg-cmake:x64-windows@2024-04-23...
Elapsed time to handle vcpkg-cmake:x64-windows: 7.62 ms
vcpkg-cmake:x64-windows package ABI: 9637351d1fd8be760c6f1c6639c45adab53bbc6219c445e19ce8c36a134635dd
Installing 2/6 vcpkg-cmake-config:x64-windows@2024-05-23...
Elapsed time to handle vcpkg-cmake-config:x64-windows: 5.77 ms
vcpkg-cmake-config:x64-windows package ABI: 0b909e7f209c13ac999053fc76af399a525c0582f879ca8add9594705525078b
Installing 3/6 libjpeg-turbo:x64-windows@3.1.0#1...
Elapsed time to handle libjpeg-turbo:x64-windows: 20.1 ms
libjpeg-turbo:x64-windows package ABI: bb02455bc7ccba75437757fc154091241a67f3379379f5ceb4a5d7e84bed7687
Installing 4/6 vcpkg-cmake-get-vars:x64-windows@2024-09-22...
Elapsed time to handle vcpkg-cmake-get-vars:x64-windows: 6.82 ms
vcpkg-cmake-get-vars:x64-windows package ABI: 28894ed939f06b7cc4ce9dfd4a7e515ba3ed21cd9adbf8ce173145a8a1b33be7
Installing 5/6 libyuv:x64-windows@1896#1...
Elapsed time to handle libyuv:x64-windows: 23.9 ms
libyuv:x64-windows package ABI: 307f2297cdfe95e171ae604ba9e19a329de64eadceb8bfd89cc5c7a330c5002b
Installing 6/6 libavif:x64-windows@1.1.1#1...
Building libavif:x64-windows@1.1.1#1...
-- Using cached AOMediaCodec-libavif-v1.1.1.tar.gz
-- Cleaning sources at D:/Dev/Repos/Vcpkg/buildtrees/libavif/src/v1.1.1-71281019e0.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source D:/Dev/Repos/Vcpkg/downloads/AOMediaCodec-libavif-v1.1.1.tar.gz
-- Applying patch dependencies.diff
-- Applying patch disable-source-utf8.patch
-- Using source at D:/Dev/Repos/Vcpkg/buildtrees/libavif/src/v1.1.1-71281019e0.clean
-- Using cached msys2-mingw-w64-x86_64-pkgconf-1~2.3.0-1-any.pkg.tar.zst
-- Using cached msys2-msys2-runtime-3.5.4-2-x86_64.pkg.tar.zst
-- Using msys root at D:/Dev/Repos/Vcpkg/downloads/tools/msys2/21caed2f81ec917b
-- Configuring x64-windows
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:127 (message):
    Command failed: "C:/Program Files/Microsoft Visual Studio/2022/Community/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe" -v
    Working Directory: D:/Dev/Repos/Vcpkg/buildtrees/libavif/x64-windows-rel/vcpkg-parallel-configure
    Error code: 1
    See logs for more information:
      D:\Dev\Repos\Vcpkg\buildtrees\libavif\config-x64-windows-dbg-CMakeCache.txt.log
      D:\Dev\Repos\Vcpkg\buildtrees\libavif\config-x64-windows-rel-CMakeCache.txt.log
      D:\Dev\Repos\Vcpkg\buildtrees\libavif\config-x64-windows-dbg-CMakeConfigureLog.yaml.log
      D:\Dev\Repos\Vcpkg\buildtrees\libavif\config-x64-windows-rel-CMakeConfigureLog.yaml.log
      D:\Dev\Repos\Vcpkg\buildtrees\libavif\config-x64-windows-out.log

Call Stack (most recent call first):
  installed/x64-windows/share/vcpkg-cmake/vcpkg_cmake_configure.cmake:269 (vcpkg_execute_required_process)
  ports/libavif/portfile.cmake:23 (vcpkg_cmake_configure)
  scripts/ports.cmake:196 (include)


error: building libavif:x64-windows failed with: BUILD_FAILED
See https://learn.microsoft.com/vcpkg/troubleshoot/build-failures?WT.mc_id=vcpkg_inproduct_cli for more information.
Elapsed time to handle libavif:x64-windows: 1.4 s
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+libavif
You can submit a new issue at:
  https://github.com/microsoft/vcpkg/issues/new?title=[libavif]+Build+error+on+x64-windows&body=Copy%20issue%20body%20from%20D%3A%2FDev%2FRepos%2FVcpkg%2Finstalled%2Fvcpkg%2Fissue_body.md

Additional Context

vcpkg --version
vcpkg package management program version 2025-02-11-bec4296bf5289dc9ce83b4f5095943e44162f9c2

config-x64-windows-out.log

@MarnixKuijs MarnixKuijs added the category:port-bug The issue is with a library, which is something the port should already support label Mar 9, 2025
@WangWeiLin-MV WangWeiLin-MV added requires:repro The issue is not currently repro-able and removed category:port-bug The issue is with a library, which is something the port should already support labels Mar 10, 2025
@WangWeiLin-MV
Copy link
Contributor

Using the latest version of vcpkg for local installation does not reproduce the issue.

Please try with latest vcpkg repository by git pull and update tools by .\bootstrap-vcpkg.bat, and clean the {VCPKG_DOWNLOADS}/tools/cmake* directories.

@MarnixKuijs
Copy link
Author

Getting the latest version of vcpkg and running .\bootstrap-vcpkg.bat and clearing any cached data still results in the same error for me. I'm on version 2025-02-11-bec4296bf5289dc9ce83b4f5095943e44162f9c2 which is, as far as I can tell, the latest version.

@MarnixKuijs
Copy link
Author

MarnixKuijs commented Mar 11, 2025

For more context in particular using the x64-windows triplet seems to be the issue, Using the x64-windows-static or x64-windows-static-md triplet works fine and results in no error.

@WangWeiLin-MV
Copy link
Contributor

... and clearing any cached data ...

It might be the cached error. Would you try it by appending the install option --binarysource=clear ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
requires:repro The issue is not currently repro-able
Projects
None yet
Development

No branches or pull requests

2 participants