summaryrefslogtreecommitdiff
path: root/pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
diff options
context:
space:
mode:
authorAdam Joseph <adam@westernsemico.com>2023-10-23 01:23:23 -0700
committerAdam Joseph <54836058+amjoseph-nixpkgs@users.noreply.github.com>2023-10-26 06:12:33 +0000
commit27a73cd1769ca05e9a1eb184edc9df9c844af733 (patch)
treecbe41ead50ed0252fddd41c206f11ab07be8d1f5 /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
parent5c7aa4a2ca9d56aa4f245072492fe1a8b7101354 (diff)
glibc: use (lib.getBin pkgsBuildBuild.glibc) to generate locales
This is an alternative resolution of the problem identified in https://github.com/NixOS/nixpkgs/pull/259964 which stated that "glibc depends on buildPackages.glibc for locale things. buildPackages.glibc depended on buildPackages.libgcc, which, since it's GCC, depends on the target's bintools, which depend on the target's glibc, which, again, depends on buildPackages.glibc, causing an infinute recursion when evaluating buildPackages.glibc when glibc hasn't come from stdenv (e.g. on musl)." The fact that we use pkgsBuildHost.glibc instead of pkgsBuildBuild.glibc to generate the locales has always been a gross hack. If we simply remove the gross hack the circularity goes away.
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions