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
..
bootstrap-files	pkgs/stdenv/linux: init powerpc64-unknown-linux-gnuabielfv2 bootstrap-files	2024-03-10 12:36:34 +01:00
bootstrap-tools	cc-wrapper: add trivialautovarinit hardening flag support	2024-02-24 12:00:09 +00:00
bootstrap-tools-musl	cc-wrapper: add trivialautovarinit hardening flag support	2024-02-24 12:00:09 +00:00
default.nix	wrapCC, wrapBintools: move expand-response-params bootstrapping out	2024-04-18 20:49:13 +02:00
make-bootstrap-tools-cross.nix	pkgs/stdenv/linux/make-bootstrap-tools-cross: Add powerpc64 entry	2024-03-04 15:01:29 +01:00
make-bootstrap-tools.nix	pkgs/top-level/release.nix: drop unused dist targets	2024-04-04 21:40:08 +01:00