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

Offen
#2,057 7 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
35/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Veraltet
Tech-Stack
c, cmake, cpp, python

Rechercherichtung

Der Fehler ist ein Linker-Problem mit OpenMP-Symbolen (GOMP_barrier, omp_get_thread_num) unter Windows mit MinGW. Sieh dir die CMake-Konfiguration in vendor/llama.cpp/ggml/src/CMakeLists.txt und die Build-Skripte für llama-cpp-python an. Überprüfe, wie OpenMP gelinkt wird, insbesondere für MinGW unter Windows. Die Behebung umfasst wahrscheinlich die Anpassung von CMake-Flags oder Linker-Flags, um die korrekte OpenMP-Bibliothek einzubinden. Teste den Build nach den Änderungen mit denselben Umgebungsvariablen.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.
Vorherrschende Sprache
Python
Sterne
10.7k
Forks
1.5k
Ø Merge
1 Std. 40 Min.
Gemergte PRs (30 T.)
5

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus abetlen/llama-cpp-python

Alle Issues in abetlen/llama-cpp-python

Ähnliche Issues

Weitere Issues zu Python

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.