Cannot install current version of llama-cpp-python 0.3.16 on Windows (backend independent)

Aberta
#2,057 7 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
35/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Estagnada
Stack de tecnologia
c, cmake, cpp, python
Domínio
backend, build-system

Direção de pesquisa

O erro é um problema do linker com símbolos do OpenMP (GOMP_barrier, omp_get_thread_num) no Windows usando MinGW. Examine a configuração do CMake em vendor/llama.cpp/ggml/src/CMakeLists.txt e os scripts de build do llama-cpp-python. Verifique como o OpenMP é vinculado, especialmente para MinGW no Windows. A correção provavelmente envolve ajustar as flags do CMake ou as flags do linker para incluir a biblioteca OpenMP correta. Teste o build com as mesmas variáveis de ambiente após as alterações.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

Prerequisites

Please answer the following questions for yourself before submitting an issue.

Expected Behavior

When installing llama-cpp-python with the respective environment variables mentioned in the docs set, the installation of the dependency should succeed.

Current Behavior

The installation failed. See the error log below.

Environment and Context

Environment variables:

  • CMAKE_GENERATOR=MinGW Makefiles
  • CMAKE_ARGS=-DGGML_OPENBLAS=on -DGGML_BLAS=ON -DGGML_BLAS_VENDOR=OpenBLAS -DGGML_OPENBLAS=on -DCMAKE_C_COMPILER=E:/Development/w64devkit/bin/gcc.exe -DCMAKE_CXX_COMPILER=E:/Development/w64devkit/bin/g++.exe

I also tried this with Vulkan and ROCm backend and got exactly the same error.

System and dependency information:

  • AMD Ryzen 7 7800X3D
  • AMD 7900 XTX
  • Operating System: Windows
  • Python version: 3.13.6
  • w64devkit version: 2.4.0
  • make version: GNU Make 4.4.1 Built for x86_64-w64-mingw32
  • g++ version: g++.exe (GCC) 15.2.0

Failure Information (for bugs)

The installation failed (see error log below). The error stays the same no matter what backend (OpenBLAS, Vulkan, ROCm) is chosen

Steps to Reproduce

  1. Set the environment variables as mentioned above
  2. Install the dependency via pip or any other package manager (I use uv sync)
  3. See the failing error message

Failure Logs

[ 38%] Linking CXX shared library ..\..\..\..\bin\ggml-cpu.dll
      cd /d C:\Users\Tobias\AppData\Local\Temp\tmppea8rsz0\build\vendor\llama.cpp\ggml\src &&
      C:\Users\Tobias\AppData\Local\uv\cache\builds-v0\.tmpqQBqx0\Lib\site-packages\cmake\data\bin\cmake.exe -E
      cmake_link_script CMakeFiles\ggml-cpu.dir\link.txt --verbose=1
      C:\Users\Tobias\AppData\Local\uv\cache\builds-v0\.tmpqQBqx0\Lib\site-packages\cmake\data\bin\cmake.exe -E rm -f
      CMakeFiles\ggml-cpu.dir/objects.a
      E:\Development\w64devkit\bin\ar.exe qc CMakeFiles\ggml-cpu.dir/objects.a @CMakeFiles\ggml-cpu.dir\objects1.rsp
      E:\Development\w64devkit\bin\g++.exe -O3 -DNDEBUG -shared -o ..\..\..\..\bin\ggml-cpu.dll
      -Wl,--out-implib,libggml-cpu.dll.a -Wl,--major-image-version,0,--minor-image-version,0 -Wl,--whole-archive
      CMakeFiles\ggml-cpu.dir/objects.a -Wl,--no-whole-archive @CMakeFiles\ggml-cpu.dir\linkLibs.rsp
      make[2]: Leaving directory 'C:/Users/Tobias/AppData/Local/Temp/tmppea8rsz0/build'
      make[1]: Leaving directory 'C:/Users/Tobias/AppData/Local/Temp/tmppea8rsz0/build'

CMake Warning (dev) at CMakeLists.txt:21 (install):
        Target ggml has PUBLIC_HEADER files but no PUBLIC_HEADER DESTINATION.
      Call Stack (most recent call first):
        CMakeLists.txt:109 (llama_cpp_python_install_target)
      This warning is for project developers.  Use -Wno-dev to suppress it.

E:\Development\w64devkit\bin/ld.exe: CMakeFiles\ggml-cpu.dir/objects.a(ggml-cpu.c.obj):ggml-cpu.c:(.text+0x31df):
      undefined reference to `GOMP_barrier'
      E:\Development\w64devkit\bin/ld.exe: CMakeFiles\ggml-cpu.dir/objects.a(ggml-cpu.c.obj):ggml-cpu.c:(.text+0x44fd):
      undefined reference to `GOMP_barrier'
      E:\Development\w64devkit\bin/ld.exe: CMakeFiles\ggml-cpu.dir/objects.a(ggml-cpu.c.obj):ggml-cpu.c:(.text+0x4587):
      undefined reference to `GOMP_barrier'
      E:\Development\w64devkit\bin/ld.exe: CMakeFiles\ggml-cpu.dir/objects.a(ggml-cpu.c.obj):ggml-cpu.c:(.text+0x4f95):
      undefined reference to `GOMP_barrier'
      E:\Development\w64devkit\bin/ld.exe: CMakeFiles\ggml-cpu.dir/objects.a(ggml-cpu.c.obj):ggml-cpu.c:(.text+0x5aad):
      undefined reference to `GOMP_single_start'
      E:\Development\w64devkit\bin/ld.exe: CMakeFiles\ggml-cpu.dir/objects.a(ggml-cpu.c.obj):ggml-cpu.c:(.text+0x5ab6):
      undefined reference to `GOMP_barrier'
      E:\Development\w64devkit\bin/ld.exe: CMakeFiles\ggml-cpu.dir/objects.a(ggml-cpu.c.obj):ggml-cpu.c:(.text+0x5abb):
      undefined reference to `omp_get_thread_num'
      E:\Development\w64devkit\bin/ld.exe: CMakeFiles\ggml-cpu.dir/objects.a(ggml-cpu.c.obj):ggml-cpu.c:(.text+0x5ae1):
      undefined reference to `omp_get_num_threads'
      E:\Development\w64devkit\bin/ld.exe: CMakeFiles\ggml-cpu.dir/objects.a(ggml-cpu.c.obj):ggml-cpu.c:(.text+0x6b40):
      undefined reference to `GOMP_parallel'
      E:\Development\w64devkit\bin/ld.exe: CMakeFiles\ggml-cpu.dir/objects.a(ggml-cpu.c.obj):ggml-cpu.c:(.text+0x90c):
      undefined reference to `GOMP_barrier'
      collect2.exe: error: ld returned 1 exit status
      make[2]: *** [vendor\llama.cpp\ggml\src\CMakeFiles\ggml-cpu.dir\build.make:341: bin/ggml-cpu.dll] Error 1
      make[1]: *** [CMakeFiles\Makefile2:350: vendor/llama.cpp/ggml/src/CMakeFiles/ggml-cpu.dir/all] Error 2
      make: *** [Makefile:135: all] Error 2

      *** CMake build failed

hint: This usually indicates a problem with the package or the build environment.
Linguagem predominante
Python
Estrelas
10.7k
Forks
1.5k
Merge médio
1h 40min
PRs com merge (30d)
5

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de abetlen/llama-cpp-python

Todas as issues de abetlen/llama-cpp-python

Issues semelhantes

Mais issues de Python

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.