2012-12-22 11:17:06 +00:00
|
|
|
{system ? builtins.currentSystem}:
|
|
|
|
|
|
|
|
|
|
let
|
2022-06-08 14:23:00 +01:00
|
|
|
inherit (releaseLib) lib;
|
|
|
|
|
releaseLib = import ../../top-level/release-lib.nix {
|
|
|
|
|
# We're not using any functions from release-lib.nix that look at
|
|
|
|
|
# supportedSystems.
|
|
|
|
|
supportedSystems = [];
|
|
|
|
|
};
|
|
|
|
|
|
2017-06-26 21:56:03 +01:00
|
|
|
make = crossSystem: import ./make-bootstrap-tools.nix {
|
2022-06-08 14:23:00 +01:00
|
|
|
pkgs = releaseLib.pkgsForCross crossSystem system;
|
top-level: Introduce `buildPackages` for resolving build-time deps
[N.B., this package also applies to the commits that follow it in the same
PR.]
In most cases, buildPackages = pkgs so things work just as before. For
cross compiling, however, buildPackages is resolved as the previous
bootstrapping stage. This allows us to avoid the mkDerivation hacks cross
compiling currently uses today.
To avoid a massive refactor, callPackage will splice together both package
sets. Again to avoid churn, it uses the old `nativeDrv` vs `crossDrv` to do
so. So now, whether cross compiling or not, packages with get a `nativeDrv`
and `crossDrv`---in the non-cross-compiling case they are simply the same
derivation. This is good because it reduces the divergence between the
cross and non-cross dataflow. See `pkgs/top-level/splice.nix` for a comment
along the lines of the preceding paragraph, and the code that does this
splicing.
Also, `forceNativeDrv` is replaced with `forceNativePackages`. The latter
resolves `pkgs` unless the host platform is different from the build
platform, in which case it resolves to `buildPackages`. Note that the
target platform is not important here---it will not prevent
`forcedNativePackages` from resolving to `pkgs`.
--------
Temporarily, we make preserve some dubious decisions in the name of preserving
hashes:
Most importantly, we don't distinguish between "host" and "target" in the
autoconf sense. This leads to the proliferation of *Cross derivations
currently used. What we ought to is resolve native deps of the cross "build
packages" (build = host != target) package set against the "vanilla
packages" (build = host = target) package set. Instead, "build packages"
uses itself, with (informally) target != build in all cases.
This is wrong because it violates the "sliding window" principle of
bootstrapping stages that shifting the platform triple of one stage to the
left coincides with the next stage's platform triple. Only because we don't
explicitly distinguish between "host" and "target" does it appear that the
"sliding window" principle is preserved--indeed it is over the reductionary
"platform double" of just "build" and "host/target".
Additionally, we build libc, libgcc, etc in the same stage as the compilers
themselves, which is wrong because they are used at runtime, not build
time. Fixing this is somewhat subtle, and the solution and problem will be
better explained in the commit that does fix it.
Commits after this will solve both these issues, at the expense of breaking
cross hashes. Native hashes won't be broken, thankfully.
--------
Did the temporary ugliness pan out? Of the packages that currently build in
`release-cross.nix`, the only ones that have their hash changed are
`*.gcc.crossDrv` and `bootstrapTools.*.coreutilsMinimal`. In both cases I
think it doesn't matter.
1. GCC when doing a `build = host = target = foreign` build (maximally
cross), still defines environment variables like `CPATH`[1] with
packages. This seems assuredly wrong because whether gcc dynamically
links those, or the programs built by gcc dynamically link those---I
have no idea which case is reality---they should be foreign. Therefore,
in all likelihood, I just made the gcc less broken.
2. Coreutils (ab)used the old cross-compiling infrastructure to depend on
a native version of itself. When coreutils was overwritten to be built
with fewer features, the native version it used would also be
overwritten because the binding was tight. Now it uses the much looser
`BuildPackages.coreutils` which is just fine as a richer build dep
doesn't cause any problems and avoids a rebuild.
So, in conclusion I'd say the conservatism payed off. Onward to actually
raking the muck in the next PR!
[1]: https://gcc.gnu.org/onlinedocs/gcc/Environment-Variables.html
2016-12-18 07:51:18 +00:00
|
|
|
};
|
2018-08-21 20:31:34 +01:00
|
|
|
in lib.mapAttrs (n: make) (with lib.systems.examples; {
|
2024-02-12 09:39:42 +00:00
|
|
|
# NOTE: Only add platforms for which there are files in `./bootstrap-files`
|
|
|
|
|
# or for which you plan to request the tarball upload soon. See the
|
|
|
|
|
# maintainers/scripts/bootstrap-files/README.md
|
|
|
|
|
# on how to request an upload.
|
2023-10-01 23:30:11 +01:00
|
|
|
# Sort following the sorting in `./default.nix` `bootstrapFiles` argument.
|
|
|
|
|
|
2023-10-01 00:42:49 +01:00
|
|
|
armv5tel-unknown-linux-gnueabi = sheevaplug;
|
|
|
|
|
armv6l-unknown-linux-gnueabihf = raspberryPi;
|
|
|
|
|
armv7l-unknown-linux-gnueabihf = armv7l-hf-multiplatform;
|
|
|
|
|
aarch64-unknown-linux-gnu = aarch64-multiplatform;
|
|
|
|
|
mipsel-unknown-linux-gnu = mipsel-linux-gnu;
|
|
|
|
|
mips64el-unknown-linux-gnuabin32 = mips64el-linux-gnuabin32;
|
|
|
|
|
mips64el-unknown-linux-gnuabi64 = mips64el-linux-gnuabi64;
|
2024-03-04 14:01:29 +00:00
|
|
|
powerpc64-unknown-linux-gnuabielfv2 = ppc64;
|
2023-10-01 00:42:49 +01:00
|
|
|
powerpc64le-unknown-linux-gnu = powernv;
|
|
|
|
|
riscv64-unknown-linux-gnu = riscv64;
|
2024-07-16 19:33:49 +01:00
|
|
|
s390x-unknown-linux-gnu = s390x;
|
2023-10-01 21:54:39 +01:00
|
|
|
|
|
|
|
|
# musl
|
2023-10-01 00:42:49 +01:00
|
|
|
aarch64-unknown-linux-musl = aarch64-multiplatform-musl;
|
|
|
|
|
armv6l-unknown-linux-musleabihf = muslpi;
|
|
|
|
|
x86_64-unknown-linux-musl = musl64;
|
2018-08-21 20:31:34 +01:00
|
|
|
})
|
