Change:
Build of failed on x86_64-linux as of . This is currently breaking python3Packages.jaxlibWithCuda. python3Packages.jaxlibWithCuda maintainers cc: maintainers cc: Other cc: n/a nixpkgs at commit This issue was automatically generated by . that created this issue. Internal tag:
I'm observing this error with many more packages (e.g. ). I'd expect it would've been introduced introduced elsewhere than in openscad commit?
I just bisected a similar bug (dm-tree failure) to
I'm not sure what to do about this... It seems like the kinda of thing people won't want to rollback, but it's also breaking a loooooot of things. cc
Can't reproduce, no build failure on my end. Hydra also has a cached built copy.
I think it's only the version that's failing
I'll see what happens if we bump in
Hopefully it is only a gcc mismatch issue.
RE: Ok, actually tensorflow and jaxlib are still pinned to and override to , so they're all pulling in . Idk about unpinning tensorflow, but I'm pretty sure we should be safe to switch jaxlib to the default cuda packages
As far as the error message goes it seems like it wants LLVM clang rather than GNU g++.
That's a good point. I think we should unpin jax from needing to use the same versions as TF. This seemed like a good idea at the time (I advocated for it), but it's proven to be a PITA since then. TF's version constraints are just so outdated. would you be opposed? I suspect that this was caused by the GCC bump, but I'm not 100% certain yet. I'm currently bisecting a different failure, but once that's done I'll try to debug this further!
Unpinning jax from the old cudaPackages and bumping the new cuda packages to gcc11 I get no more missing symbols, but I fail with:
Thanks for taking a stab at that Just to confirm: is that error within glibc or is it indicating a misuse of glibc APIs?
would you mind the derivation that you've been using? I'm curious to reproduce
good catch, the error was from: I was trying to build with updating and removing for jaxlib and jaxlib-build
Created an issue upstream:

Discussion:
version = "11.4.2" url = "https://developer.download.nvidia.com/compute/cuda/11.4.2/local_installers/cuda_11.4.2_470.57.02_linux.run" sha256 = "sha256-u9h8oOkT+DdFSnljZ0c1E83e9VUILk2G7Zo4ZZzIHwo=" <del> gcc = "gcc10" # can bump to 11 along with stdenv.cc </del> <ins> gcc = "gcc11" </ins> ["11.5"] version = "11.5.0" url = "https://developer.download.nvidia.com/compute/cuda/11.5.0/local_installers/cuda_11.5.0_495.29.05_linux.run" sha256 = "sha256-rgoWk9lJfPPYHmlIlD43lGNpANtxyY1Y7v2sr38aHkw=" <del> gcc = "gcc10" # can bump to 11 along with stdenv.cc </del> <ins> gcc = "gcc11" </ins> ["11.6"] version = "11.6.1" url = "https://developer.download.nvidia.com/compute/cuda/11.6.1/local_installers/cuda_11.6.1_510.47.03_linux.run" sha256 = "sha256-qyGa/OALdCABEyaYZvv/derQN7z8I1UagzjCaEyYTX4=" <del> gcc = "gcc10" # can bump to 11 along with stdenv.cc </del> <ins> gcc = "gcc11" </ins>

inherit (darwin.apple_sdk.frameworks) Security; }; <del> gpu-burn = callPackage ../applications/misc/gpu-burn { }; </del> <ins> gpu-burn = callPackage ../applications/misc/gpu-burn { # gpu-burn doesn't build on gcc11. CUDA 11.3 is the last version to use # pre-gcc11, in particular gcc9. cudatoolkit = cudaPackages_11_3.cudatoolkit; stdenv = gcc9Stdenv; }; </ins> greg = callPackage ../applications/audio/greg { pythonPackages = python3Packages;

librealsenseWithCuda = callPackage ../development/libraries/librealsense { cudaSupport = true; <ins> # librealsenseWithCuda doesn't build on gcc11. CUDA 11.3 is the last version # to use pre-gcc11, in particular gcc9. cudaPackages = cudaPackages_11_3; stdenv = gcc9Stdenv; </ins> }; librealsenseWithoutCuda = callPackage ../development/libraries/librealsense {

cufflinks = callPackage ../development/python-modules/cufflinks { }; <del> cupy = callPackage ../development/python-modules/cupy { }; </del> <ins> cupy = callPackage ../development/python-modules/cupy { # cupy doesn't build on gcc11. CUDA 11.3 is the last version to use # pre-gcc11, in particular gcc9. cudaPackages = pkgs.cudaPackages_11_3; }; </ins> curio = callPackage ../development/python-modules/curio { };

jaxlib-bin = callPackage ../development/python-modules/jaxlib/bin.nix { cudaSupport = pkgs.config.cudaSupport or false; <del> inherit (self.tensorflow) cudaPackages; </del> <ins> # At the time of writing (2022-04-18), `cudaPackages.nccl` is broken, so we # pin to `cudaPackages_11_6` instead. cudaPackages = pkgs.cudaPackages_11_6; </ins> }; jaxlib-build = callPackage ../development/python-modules/jaxlib { # Some platforms don't have `cudaSupport` defined, hence the need for 'or false'. cudaSupport = pkgs.config.cudaSupport or false; <del> inherit (self.tensorflow) cudaPackages; </del> <ins> # At the time of writing (2022-04-18), `cudaPackages.nccl` is broken, so we # pin to `cudaPackages_11_6` instead. cudaPackages = pkgs.cudaPackages_11_6; </ins> }; jaxlib = self.jaxlib-build; jaxlibWithCuda = self.jaxlib-build.override { cudaSupport = true; }; jaxlibWithoutCuda = self.jaxlib-build.override {