summaryrefslogtreecommitdiff
path: root/pkgs/development/python-modules/rangehttpserver
diff options
context:
space:
mode:
authorSergei Trofimovich <slyich@gmail.com>2023-01-17 19:46:33 +0000
committerSergei Trofimovich <slyich@gmail.com>2023-01-18 22:04:41 +0000
commit8f947e417ff684965bd0156c8a444b389ab9310e (patch)
tree9400f7c6f252fdf485083605b4731d88774d4f0e /pkgs/development/python-modules/rangehttpserver
parentf46ee73ba6851e458dedc78e3f0fe2c6eb099697 (diff)
pkgsCross.wasi32.pkgsBuildTarget.llvm_{{5,12},git}: disable gold plugin on wasi
In https://github.com/NixOS/nixpkgs/pull/211126 I simplified `binutils` and `libbfd` derivations to follow upstream binutils build system closer. As a result of `./configure --target=wasm32-unknown-wasi` `binutils` does not install plugin headers by default. This causes `pkgsCross.wasi32.llvm_12` (used by `firefox`) to fail the build as: [ 81%] Building CXX object tools/gold/CMakeFiles/LLVMgold.dir/gold-plugin.cpp.o /build/llvm/tools/gold/gold-plugin.cpp:38:10: fatal error: plugin-api.h: No such file or directory 38 | #include <plugin-api.h> | ^~~~~~~~~~~~~~ The change accomodates this constraint to disable plugin support for `wasi` targets.
Diffstat (limited to 'pkgs/development/python-modules/rangehttpserver')
0 files changed, 0 insertions, 0 deletions