summaryrefslogtreecommitdiff
path: root/pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
diff options
context:
space:
mode:
authorSomeone Serge <sergei.kozlukov@aalto.fi>2023-02-25 16:32:55 +0200
committerSomeone Serge <sergei.kozlukov@aalto.fi>2023-03-04 00:59:20 +0200
commit94bbbb047180b59ef6f25f4d89e7a12b5fc6db63 (patch)
tree8c1dc56c0104ae7157d53050bc2f19135072fdae /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
parent2fa2627ca9ce1ca0e622632df289a8655e6feac2 (diff)
cudaPackages: point nvcc at a compatible -ccbin
This is a hot-fix to un-break cuda-enabled packages (like tensorflow, jaxlib, faiss, opencv, ...) after the gcc11->gcc12 bump. We should probably build the whole downstream packages with a compatible stdenv (such as gcc11Stdenv for cudaPackages_11), but just pointing nvcc at the right compiler seems to do the trick We already used this hack for non-redist cudatoolkit. Now we use it more consistently. This commit also re-links cuda packages against libstdc++ from the same "compatible" gcc, rather than the current stdenv. We didn't test if this is necessary -> need to revise in further PRs. NOTE: long-term we should make it possible to override -ccbin and use e.g. clang
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions