sternenseemann b2a568906a wrapCC, wrapBintools: use runtimeShell instead of stdenv shell ... We don't need to artificially make sure that we can execute the wrapper scripts on the build platform by using stdenv's shell (which comes from buildPackages) since our cross infrastructure will get us the wrapper from buildPackages. The upside of this change is that cross-compiled wrappers (e.g. pkgsCross.aarch64-multiplatform.gcc) will actually work when executed! For bootstrapping this is also not a problem, since we have a long build->build platform chain so runtimeShell is just as good as stdenvNoCC.shell. We do fall back to old ways, though, by explicitly using the bootstrap-tools shell in stage2, so the adjacent bash is only used from stage4 onwards. This is unnecessary in principle (I'll try removing this hack in the future), but ensures this change causes zero rebuilds.		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: use runtimeShell instead of stdenv shell	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