diff options
| author | sternenseemann <sternenseemann@systemli.org> | 2022-10-10 10:59:40 +0200 |
|---|---|---|
| committer | sternenseemann <sternenseemann@systemli.org> | 2022-10-10 12:03:52 +0200 |
| commit | 0e5f7501b613b09e2f22db4a1609470fa5bdab81 (patch) | |
| tree | a770e498dd7bc28e5fa1da5605d189fbc50e3a56 /pkgs/development/python-modules/rangehttpserver | |
| parent | ad0537ab1f03d32783feb7d6f2d5906e12efa9fa (diff) | |
cbqn: always compile using clang
Investigating the build failures of CBQN on i686 and aarch64, turns up
that CBQN is broken on these platforms only with gcc. In the case of
i686 due to a codegen bug, on aarch64 gcc doesn't like some CPP macros
CBQN uses.
The deeper reason for this is that CBQN primarily is developed for and
tested with clang, so it probably saves us trouble just using clang, as
it is no real problem for us to do so (clangStdenv is quite
unproblematic for pure C builds). This should also yield faster
binaries, since CBQN apparently uses some clang-specific tricks to get
quicker code generation.
Diffstat (limited to 'pkgs/development/python-modules/rangehttpserver')
0 files changed, 0 insertions, 0 deletions
