b2a568906a
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. |
||
|---|---|---|
| .. | ||
| add-clang-cc-cflags-before.sh | ||
| add-flags.sh | ||
| add-gnat-extra-flags.sh | ||
| add-hardening.sh | ||
| cc-wrapper.sh | ||
| default.nix | ||
| fortran-hook.sh | ||
| gnat-wrapper.sh | ||
| go-wrapper.sh | ||
| setup-hook.sh | ||