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-17 23:50:16 +0200
committersternenseemann <0rpkxez4ksa01gb3typccl0i@systemli.org>2021-05-18 00:16:54 +0200
commit2d176b593b731436b4310a74c226775a16d6dee2 (patch)
tree319bfe0bd9e3dd1d31eefa0014158bbeef54d237 /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
parent8c6d8191436912231312b7b12f0cefc3fc7fb18a (diff)
gcc*: force building a cross compiler if host and target platform differ
gcc's configure system has the nasty habit (for us) of judging for itself if it is building a cross compiler (or cross compiling), but on the limited information of the build, host and target platforms' config which only contains a subset of the information we encode in `stdenv.*Platform`. The practical consequence was that prior to this change building `pkgsLLVM.buildPackages.gcc` actually fails because it refuses to use `--with-headers` with something it believes to not be a cross compiler. As a workaround we force the appropriate variable in the configure script to always be `yes` regardless of its own conditional check. At some point we probably should report this issue in some capacity, so future gcc versions don't force us into workarounds like this and acdc783418538f23cdfb671bc8fd4b1c076979bd.
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions