diff options
| author | sternenseemann <sternenseemann@systemli.org> | 2024-09-01 13:32:41 +0200 |
|---|---|---|
| committer | sternenseemann <sternenseemann@systemli.org> | 2024-09-14 17:52:09 +0200 |
| commit | b039994dad3a4288dfdffe388cf97faf39240c5a (patch) | |
| tree | 764b29a62bb0f33207d299130a6bbaecd8644c45 /pkgs/development/python-modules/httpserver | |
| parent | 35f1a5b5153066628a489e441f6a12cc07fdaef1 (diff) | |
haskell.compiler.ghc*: use matching CLANG & CC on Darwin with LLVM
The Darwin LLVM backend of GHC (which is mostly interesting for
GHC < 9.2) uses clang as configured via the CLANG environment variable
as an assembler. Since it processes outputs of clang as configured via
the CC variable, we need to make sure these versions match or risk CLANG
clang not understanding the output of CC clang.
In the past this wasn't really a problem as due to the fairly old
default clang version in the stdenv, clang 11 would be used for CC.
CLANG would always be a newer version and deal with the output without
any problems.
Ever since the upgrade of the default clang version for
darwin (bcbdb800cf7659d6ff36ac114121a056fe8c9656), CC would often be a
newer version of clang than CLANG, causing build problems in some
packages like crypton (for GHC 8.10.7 and 9.0.2 on aarch64-darwin where
the darwin LLVM backend was actually used).
Diffstat (limited to 'pkgs/development/python-modules/httpserver')
0 files changed, 0 insertions, 0 deletions