summaryrefslogtreecommitdiff
path: root/pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
diff options
context:
space:
mode:
authorsternenseemann <0rpkxez4ksa01gb3typccl0i@systemli.org>2021-05-15 17:40:24 +0200
committersternenseemann <0rpkxez4ksa01gb3typccl0i@systemli.org>2021-05-15 17:40:24 +0200
commit91cba7b0a9841b9e63aaff51cf00ea3d3e2229dd (patch)
treea244959047dfb05eb932b044ae83b69cdbfd7f53 /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
parentec10b0958d019088a84470b4ebf3a8ce393b244f (diff)
llvmPackages_{10,11,12}.compiler-rt: install resource txts to $out/share
7869d1654517c028aa76fc1dedc9b5ac301a867a changed how resource files are installed. Likely by accident, now some of the resource files are installed to $dev/include instead of $out/share. This causes the cc wrapper's resource-root to miss those files from compiler-rt as they are in a different place than expected. This commit fixes all instances of this incorrect installation for llvmPackages_10, 11 and 12 which are the only llvm package sets which link ${targetLlvmLibraries.compiler-rt.out}/share to the resource-root. For the other llvm package set this will likely also need to be fixed, but it doesn't have to have immediate urgency and doing it in two steps allows us to (hopefully) fix the chromium build without causing a darwin stdenv rebuild. The full fix can be found in #123103 and should probably be included in the next staging-next rotation.
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions