From: Jakub Czajka <jakub@ekhem.eu.org>
Date: Wed, 15 Jul 2026 11:35:49 +0000 (+0000)
Subject: TODO: Update pi bun compilation status.
X-Git-Url: https://git.ekhem.eu.org/?a=commitdiff_plain;h=refs%2Fheads%2Fworktree-106da305-6436-4634-aac7-e178f725e60a;p=guix.git

TODO: Update pi bun compilation status.

Tested pi 0.80.7 (2026-07-14), upstream now builds with Bun 1.3.14,
but the binary still crashes: SIGFPE on glibc 2.39, version "0.0.0" on
glibc 2.41. Bun still at 1.3.14 (no fix since 2026-05-13).

Co-Authored-By: Claude <noreply@anthropic.com>
---

diff --git a/TODO b/TODO
index 50a1cd0..3e94d77 100644
--- a/TODO
+++ b/TODO
@@ -8,10 +8,11 @@ TODO
   3. Add claude-code at the end, run guix build -f conf/home/claude.scm and
      get the correct hash from the "hash mismatch" error message.
 * Go back to the upstream pi release tarball once Bun's --compile bug is
-  fixed.  Bun 1.2.20-1.3.11 produces broken binaries; 1.3.14 fails
-  entirely on this system (kernel 7.0.12, glibc 2.39).  As of pi 0.80.5
-  (2026-07-09), the upstream CI still builds with Bun 1.3.10, so the
-  problem persists.  When a fixed Bun is available, just download the
+  fixed.  As of pi 0.80.7 (2026-07-14), upstream builds with Bun
+  1.3.14, but the resulting binary still crashes on this system:
+  SIGFPE on glibc 2.39, and version "0.0.0" (instead of "0.80.7") on
+  glibc 2.41.  Bun is still at 1.3.14 (no fix since 2026-05-13).
+  Kernel: 7.0.14.  When a fixed Bun is available, just download the
   tarball, extract the binary, and wrap it -- no build step needed.
   Remove the npm-install-build-system wrapper and the Node.js dependency
   in conf/home/pi.scm.