fix(nix): pin nixpkgs to system rev to fix Vulkan glibc mismatch #875

Merged
SakulFlee merged 1 commit from fix/nixpkgs-align-system into main 2026-10-18 17:00:57 +00:00
Owner

The dev shell pinned nixos-unstable from June 2026 (glibc 2.42,
Mesa 26.1.2), older than the host system (NixOS 26.11, glibc 2.44,
Mesa 26.2.4). The Vulkan loader discovered the host ICDs in
/run/opengl-driver (absolute paths to the system Mesa/LLVM built for
glibc 2.44) while the app ran against the flake's glibc 2.42, so every
driver failed with GLIBC_2.44 not found and no GPU adapter was found.

Align the engine flake's nixpkgs with the system's nixpkgs revision so
the toolchain (glibc, Mesa, vulkan-loader) matches the host graphics
stack.

The dev shell pinned nixos-unstable from June 2026 (glibc 2.42, Mesa 26.1.2), older than the host system (NixOS 26.11, glibc 2.44, Mesa 26.2.4). The Vulkan loader discovered the host ICDs in /run/opengl-driver (absolute paths to the system Mesa/LLVM built for glibc 2.44) while the app ran against the flake's glibc 2.42, so every driver failed with `GLIBC_2.44 not found` and no GPU adapter was found. Align the engine flake's nixpkgs with the system's nixpkgs revision so the toolchain (glibc, Mesa, vulkan-loader) matches the host graphics stack.
fix(nix): pin nixpkgs to system rev to fix Vulkan glibc mismatch
All checks were successful
Lint / lint (pull_request) Successful in 2m3s
3d5939aa6f
The dev shell pinned nixos-unstable from June 2026 (glibc 2.42,
Mesa 26.1.2), older than the host system (NixOS 26.11, glibc 2.44,
Mesa 26.2.4). The Vulkan loader discovered the host ICDs in
/run/opengl-driver (absolute paths to the system Mesa/LLVM built for
glibc 2.44) while the app ran against the flake's glibc 2.42, so every
driver failed with `GLIBC_2.44 not found` and no GPU adapter was found.

Align the engine flake's nixpkgs with the system's nixpkgs revision so
the toolchain (glibc, Mesa, vulkan-loader) matches the host graphics
stack.
SakulFlee deleted branch fix/nixpkgs-align-system 2026-10-18 17:00:57 +00:00
Sign in to join this conversation.
No description provided.