-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fatal error: 'ggml.h' file not found #533
Comments
@samuelint i invoke the cargo run --release --bin simple --features metal -- --n-len=2048 --prompt "<|start_header_id|>user<|end_header_id|>\n\nshare 5 reasons rust is better than c++<|eot_id|><|start_header_id|>assistant<|end_header_id|>\n\n" local ~/models/llama-3.2-3b-instruct.Q6_K.gguf |
That command works. It seem the problem is the debug build. It only works in release. How to make in work in debug? I also get the error with |
hmm interesting, i have no problems with removing the release flag and performing a build rather than a run: cargo b --bin simple --features metal |
@brittlewis12 on which commit is your |
it appears pinned to 8f1d81a0 |
@brittlewis12 I had a similar issue when running the simple example on
It was fixed after deleting everything with git clone --recursive https://github.com/utilityai/llama-cpp-rs
cd llama-cpp-rs
cargo run --release --bin simple -- --prompt "The way to kill a linux process is" hf-model TheBloke/Llama-2-7B-GGUF llama-2-7b.Q4_K_M.gguf I'm not sure why it didn't work the first time I tried, but maybe it's because the first time around I cloned the repo without the recursive flag, and after trying |
@arrowban same here on linux |
Building from project root or example.
leads to the following error:
However, building individually
llama-cpp-2
&llama-cpp-sys-2
works successfully.What need to be done to have the project built on Mac?
I've tried to explicitly declare
--features metal
and it doesn't fix the problem.I've followed steps described in the
Hacking
section of the readme https://github.com/utilityai/llama-cpp-rs/tree/main?tab=readme-ov-file#hackingThe text was updated successfully, but these errors were encountered: