diff options
| author | sternenseemann <0rpkxez4ksa01gb3typccl0i@systemli.org> | 2021-04-16 10:33:28 +0200 |
|---|---|---|
| committer | sternenseemann <0rpkxez4ksa01gb3typccl0i@systemli.org> | 2021-04-18 12:43:56 +0200 |
| commit | b90cd11c48d2c22bf7d60b1fe12cdb0040bf2823 (patch) | |
| tree | eeeb009b2f18fe1b6e084867d34cd7e1981c50ea /pkgs/development/python-modules/python-mapnik | |
| parent | 5478217883e97b74a2c96f664d6e263925e7bbcf (diff) | |
glibc: always compile with a gcc stdenv
Our glibc doesn't compile with clang and useLLVM doesn't make the stdenv
implicitly switch to musl (and arguably shouldn't do that). To make LLVM
cross compilation without patching glibc to compile with clang (which is
probably a lot of work), always compile glibc with gcc. This should
unbreak a lot of cross compilation tests, I have tested:
* tests.cross.llvm.gnu64
* tests.cross.llvm.aarch64-multiplatform
Basing against staging because this change only really makes sense if
useLLVM works with llvmPackages_7 which is only the case in staging at
the moment.
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik')
0 files changed, 0 insertions, 0 deletions