[GH-ISSUE #9656] ollama 0.5.13 build failure #6301

Open
opened 2026-04-12 17:45:08 -05:00 by GiteaMirror · 3 comments
Owner

Originally created by @x3x7 on GitHub (Mar 11, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/9656

What is the issue?

I am trying to build on a Fedora 41 workstation. The full build log is attached. Looks to be go code related but not clear what the error is.

ollama-0.5.13.log

Relevant log output


OS

Linux

GPU

No response

CPU

No response

Ollama version

No response

Originally created by @x3x7 on GitHub (Mar 11, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/9656 ### What is the issue? I am trying to build on a Fedora 41 workstation. The full build log is attached. Looks to be go code related but not clear what the error is. [ollama-0.5.13.log](https://github.com/user-attachments/files/19195617/ollama-0.5.13.log) ### Relevant log output ```shell ``` ### OS Linux ### GPU _No response_ ### CPU _No response_ ### Ollama version _No response_
GiteaMirror added the linuxbuildbug labels 2026-04-12 17:45:09 -05:00
Author
Owner

@x3x7 commented on GitHub (Mar 12, 2025):

One build problem is fixed by upgrading golang-github-dlclark-regexp2 to 1.11.5 (Fedora only had 1.4.0 available)

_build/src/github.com/ollama/ollama/model/process_text.go:122:43: undefined: regexp2.Unicode
_build/src/github.com/ollama/ollama/model/process_text_spm.go:47:49: undefined: regexp2.Unicode

By using the cmake based build the (ollama and runner) binaries are not available. How can those be created?

<!-- gh-comment-id:2717522554 --> @x3x7 commented on GitHub (Mar 12, 2025): One build problem is fixed by upgrading golang-github-dlclark-regexp2 to 1.11.5 (Fedora only had 1.4.0 available) _build/src/github.com/ollama/ollama/model/process_text.go:122:43: undefined: regexp2.Unicode _build/src/github.com/ollama/ollama/model/process_text_spm.go:47:49: undefined: regexp2.Unicode By using the cmake based build the (ollama and runner) binaries are not available. How can those be created?
Author
Owner

@x3x7 commented on GitHub (Mar 12, 2025):

I managed to build the ollama and runner binaries by explicit call for "go build". Now one more thing missing, the AMD GPU code is not build even though the cmake configuration finds the HIP compiler. For details please check the attached log (version 0.6.0 this time).

What is there needed for a build with AMD support?

ollama-0.6.0.log

<!-- gh-comment-id:2718684118 --> @x3x7 commented on GitHub (Mar 12, 2025): I managed to build the ollama and runner binaries by explicit call for "go build". Now one more thing missing, the AMD GPU code is not build even though the cmake configuration finds the HIP compiler. For details please check the attached log (version 0.6.0 this time). What is there needed for a build with AMD support? [ollama-0.6.0.log](https://github.com/user-attachments/files/19215066/ollama-0.6.0.log)
Author
Owner

@x3x7 commented on GitHub (Mar 13, 2025):

Using the -DAMDGPU_TARGETS="gfx900,gfx940,gfx941,gfx942" on the configuration cmake seems to enable the AMD support. Not sure this is the proper way though.

<!-- gh-comment-id:2721296274 --> @x3x7 commented on GitHub (Mar 13, 2025): Using the -DAMDGPU_TARGETS="gfx900,gfx940,gfx941,gfx942" on the configuration cmake seems to enable the AMD support. Not sure this is the proper way though.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#6301