cudaPackages.cuda_nvcc: patch math_functions.h signatures

[GaetanLepage]

Things done

Fix compatibility with glibc 2.42

The latest glibc (2.42) brought by the latest staging-next iteration does not play well with cuda 12.8.
This at least breaks bitsandbytes (#483507).

The cospi|sinpi|rsqrt function signatures in include/common/math_functions.h do not match glibc 2.42's.
Indeed, there they are declared with noexcept(true) which is not the case in cuda_nvcc.

This PR patches math_functions.h in cuda_nvcc's output to fix the issue.

cc @NixOS/cuda-maintainers @kirillrdy

• Built on platform:
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• Tested, as applicable:
  • NixOS tests in nixos/tests.
  • Package tests at passthru.tests.
  • Tests in lib/tests or pkgs/test for functions and "core" functionality.
• Ran nixpkgs-review on this PR. See nixpkgs-review usage.
• Tested basic functionality of all binary files, usually in ./result/bin/.
• Nixpkgs Release Notes
  • Package update: when the change is major or breaking.
• NixOS Release Notes
  • Module addition: when adding a new NixOS module.
  • Module update: when the change is significant.
• Fits CONTRIBUTING.md, pkgs/README.md, maintainers/README.md and other READMEs.

[GaetanLepage]

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review pr 484031 --extra-nixpkgs-config '{ allowUnfree = true; cudaSupport = true; }' --package python3Packages.bitsandbytes
Commit: 0fcee7419cb5778cc60605239ab41cefeb696f91

---

x86_64-linux

✅ 2 packages built:

• python3Packages.bitsandbytes
• python3Packages.bitsandbytes.dist (python3Packages.bitsandbytes.dist.dist)

[GaetanLepage]

This indeed fixes bitsandbytes' configurePhase with cudaSupport enabled.

[ConnorBaker]

Remind me, does this affect all versions of CUDA? If that includes CUDA 13.0, do we need to package cuda_crt instead of cuda_nvcc (I can't remember if cuda_crt is the one that provides the CRT headers, if we copy them into cuda_nvcc, or something else).

[ConnorBaker]

As a followup, do we need to worry about backporting these changes? I remember GLIBC was bumped to fix several vulnerabilities -- not sure if patches or the version bump would be backported.

[GaetanLepage]

As a followup, do we need to worry about backporting these changes? I remember GLIBC was bumped to fix several vulnerabilities -- not sure if patches or the version bump would be backported.

Seems like python3Packages.bitsandbytes builds fine on release-25.11 with cudaSupport.
This is expected as glibc is still at 2.40-66 there.

[SomeoneSerge]

Ah this was a simpler diff than I thought, shouldn't have blocked. That said, versionAtLeast glibc.version "2.42"?

[GaetanLepage]

Ah this was a simpler diff than I thought, shouldn't have blocked. That said, versionAtLeast glibc.version "2.42"?

Done!

[SomeoneSerge]

optionalString?

[ConnorBaker]

Ugh kill me
Can you make a hotfix and I’ll merge it

[GaetanLepage]

Sorry...
Opened #488516.