summaryrefslogtreecommitdiff
path: root/pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
diff options
context:
space:
mode:
authorJulian Stecklina <julian.stecklina@cyberus-technology.de>2024-09-26 14:57:51 +0200
committerAlyssa Ross <hi@alyssa.is>2024-12-18 16:34:07 +0100
commit48a0850c15b8123b506b4cc1d79079c518688140 (patch)
tree6833a90034598ca3d3943868c81cbe1b0e2155cd /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
parent822e728ac3205dc478680d66bb5e85ab1f3bc0cb (diff)
linux: allow building with ld.lld
Even when building with pkgsLLVM.stdenv where ld is ld.lld and not binutils ld, the build picks up binutils ld for linking. This prevents features from working that require ld.lld. The reason is that when the LD environment variable is not set, Linux defaults to `ld` as a linker and ld is: /nix/store/zznja5f8v3jafffyah1rk46vpfcn38dv-gcc-wrapper-13.3.0/bin/ld GNU ld (GNU Binutils) 2.42 This ld comes from pkgsLLVM.buildPackages.stdenv.cc. Fix by being more specific about which tools we want to build with. This just extends what manual-config.nix has already done for quite a while to avoid similar problems for other tools. It's important to pass LD and other toolchain environment variables to `make config` in generate-config.pl, because otherwise `make config` will also make decisions based on the wrong toolchain.
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions