llama.cpp 9574

[xhochy]

I would like to use the recently added MTP support for Gemma 4: ggml-org/llama.cpp#23398

llama-save-load-state is now a test and not a normal binary anymore: ggml-org/llama.cpp@40d5358

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/recipe.yaml) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipe/recipe.yaml:

• ℹ️ The recipe is not parsable by parser conda-recipe-manager. The recipe can only be automatically migrated to the new v1 format if it is parseable by conda-recipe-manager.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/27198381398. Examine the logs at this URL for more detail.}

[jjerphan]

LGTM given 🟢 CI.

[traversaro]

This just made me realized that somehow the automatic version updates seems broken here.

Furthermore, I wonder if we need to do something to enable/test the new llama unified entry point, see ggml-org/llama.cpp#23296, ggml-org/llama.cpp#23462 and Homebrew/homebrew-core#284022 .

[conda-forge-admin]

Hi! This is the friendly conda-forge automerge bot!

I considered the following status checks when analyzing this PR:

• linter: passed
• azure: passed
• github-actions: passed

Thus the PR was passing and merged! Have a great day!

[traversaro]

Checking the logs, the new llama entry point is included indeed:

 │ │   ├─ bin/llama (25.96 KiB)