Skip to content

Commit 737cc39

Browse files
committed
Document current glibc requirements
1 parent f16809f commit 737cc39

1 file changed

Lines changed: 13 additions & 0 deletions

File tree

docs/guide/troubleshooting.md

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -159,6 +159,19 @@ Debian requires one package be manually installed to support the emoji icons use
159159
apt install fonts-noto-color-emoji
160160
```
161161

162+
#### glibc Version Requirements
163+
164+
Binary Ninja targets the glibc shipped with the latest and previous-latest Ubuntu LTS releases. With the release of Ubuntu 26.04, that baseline moved from 22.04/24.04 to 24.04/26.04, which raised the minimum required glibc version for development builds. Distributions with an older glibc will fail to launch — notably Debian 12, which ships glibc 2.36 rather than the 2.38 now required.
165+
166+
If you hit this, the two supported options are:
167+
168+
* **Stay on the 5.3 stable release**, which targets an older glibc that remains compatible with Debian 12.
169+
* **Upgrade to Debian 13**, which ships glibc 2.41 and will remain compatible until Ubuntu 28.04 is released.
170+
171+
If your current install no longer runs and you need a fresh installer, download one from the [Portal](https://portal.binary.ninja/).
172+
173+
If you must run development builds on Debian 12, several unsupported work-arounds exist, though none are particularly clean. The most promising are a rootless Podman container or a `debootstrap` chroot with access to your X/Wayland server, either of which lets you run Debian 13 packages while keeping the host on Debian 12. Compiling glibc 2.38 and its dependencies yourself and injecting them via `LD_PRELOAD` or `LD_LIBRARY_PATH` is theoretically possible but significantly more effort. None of these configurations are tested or supported.
174+
162175
#### Headless Ubuntu
163176

164177
If you're having trouble getting Binary Ninja installed in a headless server install where you want to be able to X-Forward the GUI on a remote machine, the following should meet requirements (for at least 14.04 LTS):

0 commit comments

Comments
 (0)