Skip to content

Fix Firecrawl install: add ccache dependency for koffi native build - #16746

Merged
MickLesk merged 2 commits into
mainfrom
fix/firecrawl-koffi-ccache
Aug 25, 2026
Merged

Fix Firecrawl install: add ccache dependency for koffi native build#16746
MickLesk merged 2 commits into
mainfrom
fix/firecrawl-koffi-ccache

Conversation

@michelroegl-brunner

@michelroegl-brunner michelroegl-brunner commented Aug 25, 2026

Copy link
Copy Markdown
Member

✍️ Description

The Firecrawl install fails during pnpm install --frozen-lockfile while building the native koffi@2.9.0 module. On the Debian 13 (Proxmox 9.1) template, koffi has no prebuilt binary for Node 22 / linux_x64, so it builds from source. Its build script (cnoke/builder.js) auto-detects ccache and passes -DCMAKE_C_COMPILER_LAUNCHER=ccache to CMake, but a usable ccache binary isn't present when gmake runs, so every compile fails with error 127 (ccache: No such file or directory) and CMake reports the C compiler as broken.

The compiler (gcc-14/cc) itself is fine — the Go cgo library and Rust both build successfully earlier in the script. Only the ccache launcher breaks the build. Fix: add ccache to the apt dependency list so koffi's auto-detected compiler launcher works.

Authored with AI assistance: Claude Opus 4.8 (Claude Code), high reasoning level.

🔗 Related Issue

Fixes #16744

✅ Prerequisites (X in brackets)

  • Self-review completed – Code follows project standards.
  • Tested thoroughly – Changes work as expected.
  • No security risks – No hardcoded secrets, unnecessary privilege escalations, or permission issues.

🤖 AI Assistance (X in brackets)

If you used an AI tool (GitHub Copilot, Claude, ChatGPT, etc.) to write or generate any scripts in this PR, you must confirm compliance below.
Select exactly one option.

  • No AI used – Scripts were written without AI assistance.
  • AI was used – I confirm the scripts were built using AGENTS.md and .github/agents/pve-script-creator.agent.md as guidance, and the output has been reviewed and corrected to match those guidelines.

🛠️ Type of Change (X in brackets)

  • 🐞 Bug fix – Resolves an issue without breaking functionality.
  • New feature – Adds new, non-breaking functionality.
  • 💥 Breaking change – Alters existing functionality in a way that may require updates.
  • 🆕 New script – A fully functional and tested script or script set.
  • 🌍 Website update – Changes to script metadata (PocketBase/website data).
  • 🔧 Refactoring / Code Cleanup – Improves readability or maintainability without changing functionality.
  • 📝 Documentation update – Changes to README, AppName.md, CONTRIBUTING.md, or other docs.

💥 Breaking Change Advisory (only if you checked "Breaking change")

If this PR changes existing behaviour in a way that may require action before an
update, add a breaking-change advisory block to this PR body. The website and
the in-container update guard read it to tell operators exactly what to expect,
what to do first, and — with action: block — to stop an update until it's
handled. Every field is optional; the advisory auto-expires 30 days after merge.

Copy the block out of the comment below, fill it in, and paste it here:

@michelroegl-brunner
michelroegl-brunner requested a review from a team as a code owner August 25, 2026 07:56
@github-actions github-actions Bot added bugfix update script A change that updates a script labels Aug 25, 2026
MickLesk
MickLesk previously approved these changes Aug 25, 2026
Comment thread install/firecrawl-install.sh
@MickLesk
MickLesk merged commit 1bc1b0e into main Aug 25, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bugfix update script A change that updates a script

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Firecrawl] Cannot install on my Proxmox node.

3 participants