github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-06 08:02:14 -05:00
Code Issues 14.5k Packages Projects Releases 120 Wiki Activity

[GH-ISSUE #7577] Build fails and wipes parent folder if the path to the source contains a directory name with a space #30590

New Issue
Closed
opened 2026-04-22 10:23:28 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-22 10:23:28 -05:00
Owner
Copy Link

Originally created by @gautamz on GitHub (Nov 8, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/7577

Originally assigned to: @dhiltgen on GitHub.

What is the issue?

I cloned the repo and tried to build ollama on my device running Linux with Intel cpu, Nvidia GPU and CUDA installed.

The path to source was - /home/user/workspace/sourcebuild/ollama stuff/ollama

When I ran make, the "clean payload" target from the Makefile in sub-directory "llama" wiped out /home/user/workspace
The build failed.

I then tried this with path to source as - /home/user/workspace/sourcebuild/ollama_stuff/ollama
The build succeeded.

Either the path identification should be fixed, or user should be notified and allowed to decide to proceed with rm -rf ...

Please test this cautiously. I had an older backup so recovered most of my wiped files, but did lose a few recent projects.

OS

Linux

GPU

Nvidia

CPU

Intel

Ollama version

master

Originally created by @gautamz on GitHub (Nov 8, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/7577 Originally assigned to: @dhiltgen on GitHub. ### What is the issue? I cloned the repo and tried to build ollama on my device running Linux with Intel cpu, Nvidia GPU and CUDA installed. The path to source was - /home/user/workspace/sourcebuild/ollama stuff/ollama When I ran make, the "clean payload" target from the Makefile in sub-directory "llama" wiped out /home/user/workspace The build failed. I then tried this with path to source as - /home/user/workspace/sourcebuild/ollama_stuff/ollama The build succeeded. Either the path identification should be fixed, or user should be notified and allowed to decide to proceed with rm -rf ... Please test this cautiously. I had an older backup so recovered most of my wiped files, but did lose a few recent projects. ### OS Linux ### GPU Nvidia ### CPU Intel ### Ollama version master
GiteaMirror added the buildbug labels 2026-04-22 10:23:28 -05:00
GiteaMirror commented 2026-04-22 10:23:31 -05:00
Author
Owner
Copy Link

@igorschlum commented on GitHub (Nov 8, 2024):

hi @dhiltgen do you reproduce the issue?

<!-- gh-comment-id:2465665674 --> @igorschlum commented on GitHub (Nov 8, 2024): hi @dhiltgen do you reproduce the issue?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
amd
api
app
bug
build
cli
cloud
compatibility
context-length
create
docker
documentation
embeddings
feature request
feedback wanted
good first issue
gpt-oss
gpu
harmony
help wanted
image
install
intel
js
launch
linux
macos
memory
mlx
model
needs more info
networking
nvidia
ollama.com
performance
pull-request
Mirrored from GitHub Pull Request
 python
question
registry
rendering
thinking
tools
top
vulkan
windows
wsl
No Label bug build
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#30590
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?