public
/
nixpkgs
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
nixpkgs/pkgs/stdenv/linux/bootstrap-files/i686.nix

13 lines
468 B
Nix
Raw Normal View History

Update the stdenv-linux bootstrap tools
2014-10-29 09:26:29 -07:00
{
busybox = import <nix/fetchurl.nix> {
bootstrap-files: bump WIP
2019-08-12 06:22:06 -07:00
url = https://lblasc-nix-dev.s3-eu-west-1.amazonaws.com/bootstrap-tools-i686-gcc9/busybox;
sha256 = "03g3hz2ar6nz7chfwip72gvy4wd828ha9bdgg6mjs9llsc0d2izz";
Move stdenv bootstrap binaries out of the tree Commit 986f36194650e2a41451cbfb9f29ce1c66a62df3 started to use <nix/fetchurl.nix> to "download" the bootstrap binaries from the Nixpkgs tree, using the file:/// scheme. This has really bad consequences: * It makes any derivation depend on the path of the Nixpkgs tree. So evaluating a package will produce a different .drv file when run from different locations. No wonder Hydra evaluation has been so slow lately: for every Nixpkgs evaluation, it had to create tens of thousands of .drv files, even if nothing had changed. * It requires the builder to have file system access to the Nixpkgs tree. So if your tree is in your home directory, the stdenv bootstrap would probably fail. So now the binaries are downloaded from tarballs.nixos.org. Also dropped PowerPC "support".
2014-04-19 16:16:12 -07:00
executable = true;
};
linux/bootstrap: Use <nix/fetchurl> to get the static binaries Since nix-1.4, nix's corepkgs contain a fetchurl suitable for downloading the bootstrap binaries. Doing this will allow us to have a nixpkgs with no in-tree binaries without breaking the purity of the bootstrap (though for now, they are fetched in-tree until the binaries are added to nixos.org somewhere). As an additional small benefit, the in-tree binaries do not have to be hashed on every instantiation as they do now. The fetchurl in nix-1.2 and 1.3 isn't able to make binaries executable, so it can't be used for this case. In that case, attempting to build the bootstrap will show a message asking the user to manually download each file and add it to the store with nix-store --add (but the hash is ultimately the same, of course). Signed-off-by: Shea Levy <shea@shealevy.com>
2013-05-05 08:30:34 -07:00
Update the stdenv-linux bootstrap tools
2014-10-29 09:26:29 -07:00
bootstrapTools = import <nix/fetchurl.nix> {
bootstrap-files: bump WIP
2019-08-12 06:22:06 -07:00
url = https://lblasc-nix-dev.s3-eu-west-1.amazonaws.com/bootstrap-tools-i686-gcc9/bootstrap-tools.tar.xz;
sha256 = "1m142s2z7v3v6k0m3d91prp7i71hhy394jgnkd7y3z5sh15c8j28";
Finally, the new stdenv-linux. * The statically linked bootstrap tools are now automatically reproducable, just do: $ nix-build ./make-bootstrap-tools.nix The resulting binaries in result/in-nixpkgs go to stdenv/linux/bootstrap/<platform>/, and the tarballs in result/on-server go to https://svn.cs.uu.nl:12443/repos/trace/tarballs/trunk/stdenv-linux/<platform>/<revision>/. These are checked out on nix.cs.uu.nl under http://.../dist/tarballs. * The statically linked libraries all use dietlibc now (except patchelf and glibc), so they are much smaller. This is especially nice for the tools in the Nixpkgs tree, since it makes Nixpkgs tarballs smaller. * Use Binutils 2.17 and GCC 4.1.1 for the bootstrap. * The stdenv is now based on Glibc 2.5. I hope it works ;-) svn path=/nixpkgs/trunk/; revision=6803
2006-10-23 07:27:34 -07:00
};
}