Build failure: rocmPackages.llvm.libcxx

[NullCub3]

Nixpkgs version

• Unstable (25.05)

Steps to reproduce

nix build github:nixos/nixos-unstable#rocmPackages.llvm.libcxx
or
hardware.amdgpu.opencl.enable = true

Can Hydra reproduce this build failure?

Yes, Hydra can reproduce this build failure.

Link to Hydra build job

https://hydra.nixos.org/build/286037127

Relevant log output

not sure what exactly to copy and the log is massive:
https://gist.github.com/NullCub3/7f2b5355246a47bff8ad09b1cb3b3a08

Additional context

Fails in checkPhase

System metadata

• system: "x86_64-linux"
• host os: Linux 6.6.71, NixOS, 25.05 (Warbler), 25.05.20250121.9e4d519
• multi-user?: yes
• sandbox: yes
• version: nix-env (Lix, like Nix) 2.91.1 System type: x86_64-linux Additional system types: i686-linux, x86_64-v1-linux, x86_64-v2-linux, x86_64-v3-linux Features: gc, signed-caches System configuration file: /etc/nix/nix.conf User configuration files: /home/nullcube/.config/nix/nix.conf:/etc/xdg/nix/nix.conf:/home/nullcube/.local/share/flatpak/exports/etc/xdg/nix/nix.conf:/var/lib/flatpak/exports/etc/xdg/nix/nix.conf:/home/nullcube/.nix-profile/etc/xdg/nix/nix.conf:/nix/profile/etc/xdg/nix/nix.conf:/home/nullcube/.local/state/nix/profile/etc/xdg/nix/nix.conf:/etc/profiles/per-user/nullcube/etc/xdg/nix/nix.conf:/nix/var/nix/profiles/default/etc/xdg/nix/nix.conf:/run/current-system/sw/etc/xdg/nix/nix.conf Store directory: /nix/store State directory: /nix/var/nix Data directory: /nix/store/s45cr5pmmg81v1pms4la9ziq5w799afs-lix-2.91.1/share
• nixpkgs: /nix/store/l9nb64iii15y0nr37qrs1cfm6rlpg6gh-source

Notify maintainers

@acowley @lovesegfault @Madouura @Flakebi @mschwaig

---

Note for maintainers: Please tag this issue in your pull request description. (i.e. Resolves #ISSUE.)

I assert that this issue is relevant for Nixpkgs

• I assert that this is a bug and not a support request.
• I assert that this is not a duplicate of an existing issue.
• I assert that I have read the NixOS Code of Conduct and agree to abide by it.

Is this issue important to you?

Add a 👍 reaction to issues you find important.

[mschwaig]

I don't have time to look into this right now.

Does anybody already know why this started failing, or have a good guess?

If not I think it might make sense to bisect it to find the commit that introduces the failure.