summaryrefslogtreecommitdiff
path: root/pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
diff options
context:
space:
mode:
authorSergei Trofimovich <slyich@gmail.com>2023-07-26 16:23:27 +0100
committerSergei Trofimovich <slyich@gmail.com>2023-07-26 16:40:42 +0100
commit3d66844c2de9f7d2e11e78225cfc7dcdd67109d7 (patch)
tree8803004db59c270558eca07d251198fe135829b8 /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
parentb4a5c1a43a6320394d2820623ae63b35aa5e0fe9 (diff)
gcc: revert "do not install sys-include headers for cross-compilers."
The change reverts commit 7df4387ebdc9f5293fad04480391e8743c312a3b A few reasons to revert the commit: 1. The change was not enough to restore `-idirafter` override semantic to match unwrapped compiler. 2. The change broke override semantics for cross-compilers 3. The change made override semantics different between cross-compiler and native compiler All of three have some overlap between, but I think it's important to call all of them out. The main fallout is the uboot builds, reported by cynerd. Used the following test to check the override recovery: $ nix shell github:NixOS/nixpkgs/release-22.05#pkgsCross.aarch64-multiplatform.stdenv.cc $$ cat stdio.h # empty $$ printf "#include <stdio.h>" | aarch64-unknown-linux-gnu-gcc -E - -o - -idirafter . >/dev/null; echo $? 0 It failed before the change and succeded after.
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions