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
add-hardening.sh	cc-wrapper: add trivialautovarinit hardening flag support	2024-02-24 12:00:09 +00:00
cc-wrapper.sh
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
go-wrapper.sh
setup-hook.sh	mkDerivation, bintools-wrapper: move defaultHardeningFlags determination to bintools-wrapper	2023-12-09 16:30:45 +00:00