nixpkgs/pkgs/build-support/cc-wrapper
sternenseemann 7be562d046 wrapCC, wrapBintools: move expand-response-params bootstrapping out
The cc and bintools wrapper contained ad hoc bootstrapping logic for
expand-response-params (which was callPackage-ed in a let binding). This
lead to the strange situation that the bootstrapping logic related to
expand-response-params is split between the wrapper derivations (where
it is duplicated) and the actual stdenv bootstrapping.

To clean this up, the wrappers simply should take expand-response-params
as an ordinary input: They need an adjacent expand-response-params (i.e.
one that runs on their host platform), but don't care about the how.
Providing this is only problematic during stdenv bootstrapping where we
have to pull it from the previous stage at times.
2024-04-18 20:49:13 +02:00
..
add-clang-cc-cflags-before.sh clang: don't set -march for overridden target 2024-03-01 09:51:49 +01:00
add-flags.sh
add-gnat-extra-flags.sh cc-wrapper: Fix gnatmake wrapper 2023-01-07 18:32:12 +11:00
add-hardening.sh cc-wrapper: add trivialautovarinit hardening flag support 2024-02-24 12:00:09 +00:00
cc-wrapper.sh cc-wrapper: Use MacOS compatible mktemp command 2023-10-05 10:44:34 +02:00
default.nix wrapCC, wrapBintools: move expand-response-params bootstrapping out 2024-04-18 20:49:13 +02:00
fortran-hook.sh mkDerivation, bintools-wrapper: move defaultHardeningFlags determination to bintools-wrapper 2023-12-09 16:30:45 +00:00
gnat-wrapper.sh cc-wrapper: Wrap/link all other GNAT commands 2023-01-07 18:32:12 +11:00
go-wrapper.sh gccgo: wrap go binary (#207670) 2023-01-20 14:31:54 +01:00
setup-hook.sh mkDerivation, bintools-wrapper: move defaultHardeningFlags determination to bintools-wrapper 2023-12-09 16:30:45 +00:00