summaryrefslogtreecommitdiff
path: root/pkgs/development/python-modules/rangehttpserver
diff options
context:
space:
mode:
authorSergei Trofimovich <slyich@gmail.com>2024-11-01 09:32:17 +0000
committerSergei Trofimovich <slyich@gmail.com>2024-11-25 09:11:38 +0000
commit90474914ee2c8f592342d3e3cc16e0e7693479f8 (patch)
tree1736346c36e771def9920d027a1f9c668bef0801 /pkgs/development/python-modules/rangehttpserver
parent988507244d59c582c4f7e72b1318961c03e14c30 (diff)
gcc: do not allow version skew when cross-building gcc
When `gcc` is cross-built (`build` != `target` && `host` == `target`) `gcc` assumes that it has a compatible cross-compiler in the environment that can build target libraries. Version of a cross-compiler has to match the compiler being cross-built as libraries frequently use fresh compiler features, like `-std=c++26` or target-specific types like `_Bfloat16`. Version mismatch causes build failures like: https://github.com/NixOS/nixpkgs/issues/351905 Similar problems (but on a smaller scale) happen when a `gcc` cross-compiler is built (`build` == `host` && `host` != `target`) built by a mismatching version of a native compiler (`build` == `host` && `host` == `target`). That was worked around by forcing `gcc9Stdenv` for older compiler versions. Let's fix both problems by requiring the same compiler version for cross-case. Closes: https://github.com/NixOS/nixpkgs/issues/351905
Diffstat (limited to 'pkgs/development/python-modules/rangehttpserver')
0 files changed, 0 insertions, 0 deletions