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

[gperf] Build failure #44565

Open
zeozcb opened this issue Mar 23, 2025 · 2 comments
Open

[gperf] Build failure #44565

zeozcb opened this issue Mar 23, 2025 · 2 comments
Assignees
Labels
category:question This issue is a question

Comments

@zeozcb
Copy link

zeozcb commented Mar 23, 2025

Operating system

Windows

Compiler

Clang

Steps to reproduce the behavior

git clone --recursive https://github.com/tdlib/telegram-bot-api.git
cd telegram-bot-api
git clone https://github.com/Microsoft/vcpkg.git
cd vcpkg
./bootstrap-vcpkg.bat
./vcpkg.exe install gperf:x64-windows openssl:x64-windows zlib:x64-windows
cd ..
Remove-Item build -Force -Recurse -ErrorAction SilentlyContinue
mkdir build
cd build
cmake -A x64 -DCMAKE_INSTALL_PREFIX:PATH=.. -DCMAKE_TOOLCHAIN_FILE:FILEPATH=../vcpkg/scripts/buildsystems/vcpkg.cmake ..
cmake --build . --target install --config Release
cd ../..
dir telegram-bot-api/bin/telegram-bot-api*

Failure logs

CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:127 (message):
    Command failed: C:/Users/zeo/telegram-bot-api/vcpkg/downloads/tools/ninja/1.12.1-windows/ninja.exe -v
    Working Directory: C:/Users/zeo/telegram-bot-api/vcpkg/buildtrees/gperf/x64-windows-rel/vcpkg-parallel-configure
    Error code: 1
    See logs for more information:
      C:\Users\zeo\telegram-bot-api\vcpkg\buildtrees\gperf\config-x64-windows-dbg-CMakeCache.txt.log
      C:\Users\zeo\telegram-bot-api\vcpkg\buildtrees\gperf\config-x64-windows-rel-CMakeCache.txt.log
      C:\Users\zeo\telegram-bot-api\vcpkg\buildtrees\gperf\config-x64-windows-dbg-CMakeConfigureLog.yaml.log
      C:\Users\zeo\telegram-bot-api\vcpkg\buildtrees\gperf\config-x64-windows-rel-CMakeConfigureLog.yaml.log
      C:\Users\zeo\telegram-bot-api\vcpkg\buildtrees\gperf\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/gperf/portfile.cmake:19 (vcpkg_cmake_configure)
  scripts/ports.cmake:203 (include)


error: building gperf: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 gperf:x64-windows: 7.1 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+gperf
You can submit a new issue at:
  https://github.com/microsoft/vcpkg/issues/new?title=[gperf]+Build+error+on+x64-windows&body=Copy%20issue%20body%20from%20C%3A%2FUsers%2Fzeo%2Ftelegram-bot-api%2Fvcpkg%2Finstalled%2Fvcpkg%2Fissue_body.md

config-x64-windows-out.log

Additional context

No response

@zeozcb zeozcb added the category:port-bug The issue is with a library, which is something the port should already support label Mar 23, 2025
@autoantwort
Copy link
Contributor

You have to install the windows SDK

@JonLiu1993
Copy link
Member

Thanks for posting this issue. Please make sure you have the following installed.

  • Visual Studio Desktop development with C++.
  • Windows 10 SDK or Windows 11 SDK.
CMake Error at C:/Program Files/CMake/share/cmake-4.0/Modules/CMakeTestCCompiler.cmake:67 (message):
  The C compiler

    "C:/Program Files (x86)/Microsoft Visual Studio/2019/BuildTools/VC/Tools/MSVC/14.29.30133/bin/Hostx64/x64/cl.exe"

  is not able to compile a simple test program.

@JonLiu1993 JonLiu1993 added category:question This issue is a question and removed category:port-bug The issue is with a library, which is something the port should already support labels Mar 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:question This issue is a question
Projects
None yet
Development

No branches or pull requests

3 participants