2017-02-07 17:25:01 +00:00
|
|
|
/* This file defines some basic smoke tests for cross compilation.
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
{ # The platforms *from* which we cross compile.
|
|
|
|
|
supportedSystems ? [ "x86_64-linux" "x86_64-darwin" ]
|
2017-01-14 19:25:01 +00:00
|
|
|
, # Strip most of attributes when evaluating to spare memory usage
|
|
|
|
|
scrubJobs ? true
|
|
|
|
|
}:
|
|
|
|
|
|
|
|
|
|
with import ./release-lib.nix { inherit supportedSystems scrubJobs; };
|
|
|
|
|
|
2010-03-09 14:14:30 +00:00
|
|
|
let
|
|
|
|
|
nativePlatforms = linux;
|
|
|
|
|
|
2017-05-17 20:07:04 +00:00
|
|
|
common = {
|
|
|
|
|
buildPackages.binutils = nativePlatforms;
|
|
|
|
|
gmp = nativePlatforms;
|
2017-05-18 10:55:08 +00:00
|
|
|
libcCross = nativePlatforms;
|
2010-03-09 14:14:30 +00:00
|
|
|
};
|
2010-03-09 10:33:31 +00:00
|
|
|
|
2017-05-18 14:41:58 +00:00
|
|
|
gnuCommon = lib.recursiveUpdate common {
|
2016-12-26 22:42:48 +00:00
|
|
|
buildPackages.gccCrossStageFinal = nativePlatforms;
|
2017-05-17 20:07:04 +00:00
|
|
|
coreutils = nativePlatforms;
|
2010-03-09 14:14:30 +00:00
|
|
|
};
|
|
|
|
|
|
2017-05-18 14:41:58 +00:00
|
|
|
linuxCommon = lib.recursiveUpdate gnuCommon {
|
2017-05-22 20:36:59 +00:00
|
|
|
buildPackages.gdb = nativePlatforms;
|
2010-03-09 14:14:30 +00:00
|
|
|
|
2017-05-17 20:07:04 +00:00
|
|
|
bison = nativePlatforms;
|
|
|
|
|
busybox = nativePlatforms;
|
|
|
|
|
dropbear = nativePlatforms;
|
|
|
|
|
ed = nativePlatforms;
|
|
|
|
|
ncurses = nativePlatforms;
|
|
|
|
|
patch = nativePlatforms;
|
|
|
|
|
};
|
2017-05-17 15:04:27 +00:00
|
|
|
|
2017-05-18 14:41:58 +00:00
|
|
|
windowsCommon = lib.recursiveUpdate gnuCommon {
|
2017-05-17 15:04:27 +00:00
|
|
|
boehmgc = nativePlatforms;
|
|
|
|
|
guile_1_8 = nativePlatforms;
|
|
|
|
|
libffi = nativePlatforms;
|
|
|
|
|
libtool = nativePlatforms;
|
|
|
|
|
libunistring = nativePlatforms;
|
|
|
|
|
windows.wxMSW = nativePlatforms;
|
|
|
|
|
};
|
|
|
|
|
|
2017-05-17 20:07:04 +00:00
|
|
|
darwinCommon = {
|
|
|
|
|
buildPackages.binutils = darwin;
|
|
|
|
|
};
|
|
|
|
|
|
2010-03-09 14:14:30 +00:00
|
|
|
in
|
2010-03-09 10:33:31 +00:00
|
|
|
|
2016-12-25 16:11:12 +00:00
|
|
|
{
|
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
|
|
|
# These derivations from a cross package set's `buildPackages` should be
|
|
|
|
|
# identical to their vanilla equivalents --- none of these package should
|
|
|
|
|
# observe the target platform which is the only difference between those
|
|
|
|
|
# package sets.
|
2016-12-25 18:50:53 +00:00
|
|
|
ensureUnaffected = let
|
|
|
|
|
# Absurd values are fine here, as we are not building anything. In fact,
|
|
|
|
|
# there probably a good idea to try to be "more parametric" --- i.e. avoid
|
|
|
|
|
# any special casing.
|
|
|
|
|
crossSystem = {
|
2017-05-23 05:44:27 +00:00
|
|
|
config = "mips64el-apple-windows-gnu";
|
|
|
|
|
libc = "glibc";
|
2016-12-25 18:50:53 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
|
|
# Converting to a string (drv path) before checking equality is probably a
|
|
|
|
|
# good idea lest there be some irrelevant pass-through debug attrs that
|
|
|
|
|
# cause false negatives.
|
|
|
|
|
testEqualOne = path: system: let
|
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
|
|
|
f = path: attrs: builtins.toString (lib.getAttrFromPath path (allPackages attrs));
|
2017-02-09 21:09:47 +00:00
|
|
|
in assertTrue (
|
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
|
|
|
f path { inherit system; }
|
|
|
|
|
==
|
2017-04-18 00:22:37 +00:00
|
|
|
f (["buildPackages"] ++ path) { inherit system crossSystem; }
|
2017-02-09 21:09:47 +00:00
|
|
|
);
|
2016-12-25 18:50:53 +00:00
|
|
|
|
|
|
|
|
testEqual = path: systems: forAllSupportedSystems systems (testEqualOne path);
|
|
|
|
|
|
|
|
|
|
mapTestEqual = lib.mapAttrsRecursive testEqual;
|
|
|
|
|
|
|
|
|
|
in mapTestEqual {
|
|
|
|
|
boehmgc = nativePlatforms;
|
|
|
|
|
libffi = nativePlatforms;
|
|
|
|
|
libiconv = nativePlatforms;
|
|
|
|
|
libtool = nativePlatforms;
|
|
|
|
|
zlib = nativePlatforms;
|
|
|
|
|
readline = nativePlatforms;
|
|
|
|
|
libxml2 = nativePlatforms;
|
|
|
|
|
guile = nativePlatforms;
|
|
|
|
|
};
|
|
|
|
|
|
2017-05-23 22:04:15 +00:00
|
|
|
crossIphone64 = mapTestOnCross lib.systems.examples.iphone64 darwinCommon;
|
2017-02-07 17:25:01 +00:00
|
|
|
|
2017-05-23 22:04:15 +00:00
|
|
|
crossIphone32 = mapTestOnCross lib.systems.examples.iphone32 darwinCommon;
|
2016-12-25 18:50:53 +00:00
|
|
|
|
2016-12-25 16:11:12 +00:00
|
|
|
/* Test some cross builds to the Sheevaplug */
|
2017-05-23 22:04:15 +00:00
|
|
|
crossSheevaplugLinux = mapTestOnCross lib.systems.examples.sheevaplug (linuxCommon // {
|
2016-12-26 22:42:48 +00:00
|
|
|
ubootSheevaplug = nativePlatforms;
|
2016-12-25 16:11:12 +00:00
|
|
|
});
|
2010-03-09 14:14:30 +00:00
|
|
|
|
2016-12-25 16:11:12 +00:00
|
|
|
/* Test some cross builds on 32 bit mingw-w64 */
|
2017-05-23 22:04:15 +00:00
|
|
|
crossMingw32 = mapTestOnCross lib.systems.examples.mingw32 windowsCommon;
|
2016-12-25 16:11:12 +00:00
|
|
|
|
|
|
|
|
/* Test some cross builds on 64 bit mingw-w64 */
|
2017-05-23 22:04:15 +00:00
|
|
|
crossMingwW64 = mapTestOnCross lib.systems.examples.mingwW64 windowsCommon;
|
2010-09-02 18:41:48 +00:00
|
|
|
|
2016-12-25 16:11:12 +00:00
|
|
|
/* Linux on the fuloong */
|
2017-05-23 22:04:15 +00:00
|
|
|
fuloongminipc = mapTestOnCross lib.systems.examples.fuloongminipc linuxCommon;
|
2016-12-25 16:11:12 +00:00
|
|
|
|
|
|
|
|
/* Linux on Raspberrypi */
|
2017-05-23 22:04:15 +00:00
|
|
|
rpi = mapTestOnCross lib.systems.examples.raspberryPi (linuxCommon // {
|
2016-12-26 22:42:48 +00:00
|
|
|
vim = nativePlatforms;
|
|
|
|
|
unzip = nativePlatforms;
|
|
|
|
|
ddrescue = nativePlatforms;
|
|
|
|
|
lynx = nativePlatforms;
|
|
|
|
|
patchelf = nativePlatforms;
|
|
|
|
|
buildPackages.binutils = nativePlatforms;
|
|
|
|
|
mpg123 = nativePlatforms;
|
2017-05-17 20:07:04 +00:00
|
|
|
});
|
2016-07-17 21:04:51 +00:00
|
|
|
|
2016-12-25 16:11:12 +00:00
|
|
|
|
|
|
|
|
/* Cross-built bootstrap tools for every supported platform */
|
|
|
|
|
bootstrapTools = let
|
|
|
|
|
tools = import ../stdenv/linux/make-bootstrap-tools-cross.nix { system = "x86_64-linux"; };
|
2017-01-15 19:06:35 +00:00
|
|
|
maintainers = [ lib.maintainers.dezgeg ];
|
|
|
|
|
mkBootstrapToolsJob = drv: hydraJob' (lib.addMetaAttrs { inherit maintainers; } drv);
|
|
|
|
|
in lib.mapAttrsRecursiveCond (as: !lib.isDerivation as) (name: mkBootstrapToolsJob) tools;
|
2016-12-25 16:11:12 +00:00
|
|
|
}
|