frob
frob
@SDAIer Can this issue be closed?
Since 12.7 [wasn't released](https://developer.nvidia.com/cuda-toolkit-archive) it's not surprising. But builds fine with 12.8. The released binaries ship with 12.8 and 13.1. ```console $ sudo aptitude install cuda-toolkit-12-8 && mkdir 0.12.10 &&...
> -- The C compiler identification is GNU 13.2.0 > -- The CXX compiler identification is GNU 13.2.0
```console $ mkdir 0.12.10 && cd 0.12.10 && git clone https://github.com/ollama/ollama -b v0.12.10 . && CC=gcc-14 CXX=g++-14 PATH=/usr/local/cuda-12.8/bin:$PATH cmake -B build && cmake --build build Cloning into '.'... ... --...
If you provide build information as demonstrated it might be possible to pinpoint the issue. The various `CMakeConfigureLog.yaml` files in the build (sub-)directories may also be useful.
https://github.com/ollama/ollama/issues/13075#issuecomment-3527024193
```console $ curl -sL https://github.com/ollama/ollama/archive/refs/tags/v0.12.10.tar.gz | tar zxf - && cd ollama-0.12.10 && CC=gcc-13 CXX=g++-13 PATH=/usr/local/cuda-12.9/bin:$PATH cmake -B build && cmake --build build -- The C compiler identification is GNU...
You would be in a better position to determine inconsistency than I. For example, `CMAKE_CUDA_COMPILER` doesn't match the `working CUDA compiler` line in the build log. I don't know what...
> CMAKE_CUDA_COMPILER does match! Don't you know how update-alternatives works? The directory /usr/local/cuda is a symlink that points to the active CUDA toolkit directory. If it's the same, why are...
Your're right, I don't SuSE. I had a little bit of spare time this evening and took a look. I spun up a SuSE VM. ```console rick@ddr4-suse:~> cat /etc/os-release NAME="openSUSE...