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

[tiff] build failure #38039

Closed
Tunghohin opened this issue Apr 8, 2024 · 2 comments
Closed

[tiff] build failure #38039

Tunghohin opened this issue Apr 8, 2024 · 2 comments
Assignees
Labels
category:port-bug The issue is with a library, which is something the port should already support

Comments

@Tunghohin
Copy link

Operating system

Windows11

Compiler

MSVC

Steps to reproduce the behavior

vcpkg install qt5-imageformats[tiff]

Failure logs

Computing installation plan...
The following packages will be built and installed:
qt5-imageformats[core,tiff,webp]:[email protected]#1

  • tiff[core,jpeg,lzma,zip]:[email protected]#4
    Additional packages (*) will be modified to complete this operation.
    Detecting compiler hash for triplet x64-windows...
    -- Automatically setting %HTTP(S)_PROXY% environment variables to "127.0.0.1:7890".
    Compiler found: C:/Program Files/Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.39.33519/bin/Hostx64/x64/cl.exe
    Restored 0 package(s) from C:\Users\MSN\AppData\Local\vcpkg\archives in 76.4 us. Use --debug to see more details.
    Installing 1/2 tiff[core,jpeg,lzma,zip]:[email protected]#4...
    Building tiff[core,jpeg,lzma,zip]:[email protected]#4...
    -- Using cached libtiff-libtiff-v4.6.0.tar.gz.
    -- Cleaning sources at C:/Users/MSN/vcpkg/buildtrees/tiff/src/v4.6.0-cea7694842.clean. Use --editable to skip cleaning for the packages you specify.
    -- Extracting source C:/Users/MSN/vcpkg/downloads/libtiff-libtiff-v4.6.0.tar.gz
    -- Applying patch FindCMath.patch
    -- Applying patch requires-lerc.patch
    -- Using source at C:/Users/MSN/vcpkg/buildtrees/tiff/src/v4.6.0-cea7694842.clean
    -- Found external ninja('1.11.0').
    -- Configuring x64-windows
    CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:112 (message):
    Command failed: "C:/Program Files/Microsoft Visual Studio/2022/Community/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe" -v
    Working Directory: C:/Users/MSN/vcpkg/buildtrees/tiff/x64-windows-rel/vcpkg-parallel-configure
    Error code: 1
    See logs for more information:
    C:\Users\MSN\vcpkg\buildtrees\tiff\config-x64-windows-dbg-CMakeCache.txt.log
    C:\Users\MSN\vcpkg\buildtrees\tiff\config-x64-windows-rel-CMakeCache.txt.log
    C:\Users\MSN\vcpkg\buildtrees\tiff\config-x64-windows-out.log

Call Stack (most recent call first):
installed/x64-windows/share/vcpkg-cmake/vcpkg_cmake_configure.cmake:252 (vcpkg_execute_required_process)
ports/tiff/portfile.cmake:33 (vcpkg_cmake_configure)
scripts/ports.cmake:175 (include)

error: building tiff:x64-windows failed with: BUILD_FAILED
Elapsed time to handle tiff:x64-windows: 7.6 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+tiff
You can submit a new issue at:
https://github.com/microsoft/vcpkg/issues/new?title=[tiff]+Build+error+on+x64-windows&body=Copy+issue+body+from+C%3A%2FUsers%2FMSN%2Fvcpkg%2Finstalled%2Fvcpkg%2Fissue_body.md

Additional context

According to the backtrace of the cmake log, it was found that the crash occurred in this function(line 38 set_and_check)
屏幕截图 2024-04-08 145046

The error version log shows that the include dir for WebP is not correct.

Modify line 38, the build error is fixed, the cmake log when the error occurred has been overwritten.

I've modified this

set_and_check(WebP_INCLUDE_DIR "${PACKAGE_${CMAKE_FIND_PACKAGE_NAME}_COUNTER_1}/include")

to this

set_and_check(WebP_INCLUDE_DIR "${PACKAGE_${CMAKE_FIND_PACKAGE_NAME}_COUNTER_1}/${VCPKG_TARGET_TRIPLET}/include")
@Tunghohin Tunghohin added the category:port-bug The issue is with a library, which is something the port should already support label Apr 8, 2024
@Osyotr
Copy link
Contributor

Osyotr commented Apr 8, 2024

#37968

@WangWeiLin-MV WangWeiLin-MV self-assigned this Apr 8, 2024
@WangWeiLin-MV
Copy link
Contributor

Duplicate of #37968

@WangWeiLin-MV WangWeiLin-MV marked this as a duplicate of #37968 Apr 8, 2024
@WangWeiLin-MV WangWeiLin-MV closed this as not planned Won't fix, can't repro, duplicate, stale Apr 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:port-bug The issue is with a library, which is something the port should already support
Projects
None yet
Development

No branches or pull requests

3 participants