Skip to content

chore(vendor): pin llama.cpp to the PrismML fork at 9a9394a8 - #25

Closed
ykhrustalev wants to merge 2 commits into
mainfrom
ykhrustalev/pin-llamacpp-prismml-fork
Closed

ykhrustalev wants to merge 2 commits into
mainfrom
ykhrustalev/pin-llamacpp-prismml-fork

Conversation

@ykhrustalev

@ykhrustalev ykhrustalev commented Sep 24, 2026 •

Copy link
Copy Markdown
Member

Problem
Plans need an iOS build to target llamacpp_ios_pipette at github.com/PrismML-Eng/llama.cpp 9a9394a895b96003ca842a6041cb28ac49a108f7 with private_thermal = true. The submodule is shared, but Android still reports the upstream URL, so collect results only from the iOS archive this branch produces.

Solution

  • Points vendor/llama.cpp at the PrismML fork, pinned to 9a9394a8
  • Drops vendor/llama.cpp.tag, because the fork's prism-b* tags aren't bNNNN, so the build reports as untagged
  • Stamps and submits the full sha, so the headless runtime check accepts the plan's full-sha pin
  • Reports the fork's URL from Runtime.thisBuild instead of the upstream default
  • Raises the iOS model fetch deadline from 30 minutes to 4 hours, so a ~6 GB GGUF can finish on a slow link

Testing

  • ios/patches/001-ggml-metal-oom-nullcheck.patch applies cleanly to the fork
  • ./ios/build-llama.sh sim builds and stamps untagged(commit: "9a9394a8…"); 911 iOS unit tests pass

Lets a plan target llamacpp_ios_pipette at github.com/PrismML-Eng/llama.cpp
9a9394a895b96003ca842a6041cb28ac49a108f7. The fork has no bNNNN tag, so the
build stamps and submits the full sha, and descriptors name the fork's URL.
A 5.95 GB GGUF needed ~3.4 MB/s sustained to land inside 30 minutes, and a
timed-out foreground pull keeps nothing, so every retry restarted from zero.
@ykhrustalev

Copy link
Copy Markdown
Member Author

Closing: this branch existed to hand-sign and install a PrismML-fork iOS build on boston-iphone-17pro-1..5 (internal-pipette-farm#100, now closed). Those phones now run behind pipette-ios-proxy in version mode, which installs only builds the internal releases bucket publishes, so a branch archive cannot reach them. Reopen if fork builds get a publishing path.

@ykhrustalev ykhrustalev closed this Oct 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant