2006-08-26 01:53:26 +04:00
|
|
|
Creating a new static stdenv
|
|
|
|
----------------------------
|
|
|
|
|
|
|
|
When Nix is ported to a new (Linux) platform and you want to have a completely
|
|
|
|
pure setup for the stdenv (for example for NixOS) it is necessary to rebuild
|
|
|
|
the static tools.
|
2006-08-26 03:34:31 +04:00
|
|
|
|
|
|
|
The challenge is that there is no Nix environment yet, for bootstrapping.
|
|
|
|
The first task is to create all the tools that are necessary. For most tools
|
|
|
|
there are ready made Nix expressions.
|
|
|
|
|
|
|
|
|
|
|
|
GCC
|
|
|
|
|
|
|
|
There is an expression gcc-static-3.4. Depending on whether or not you already
|
|
|
|
have an environment built with Nix (x86-linux: yes, rest: not yet) you should
|
|
|
|
set the noSysDirs parameter in all-packages.nix. If there is an environment,
|
|
|
|
leave it, but if the system is still impure (like most systems), set noSysDirs
|
|
|
|
to false.
|
2006-08-26 13:48:21 +04:00
|
|
|
|
|
|
|
bash
|
|
|
|
|
|
|
|
There is an expression for bash-static. Simply build it.
|
|
|
|
|
|
|
|
bzip2
|
|
|
|
|
|
|
|
There is an expression for bzip2-static. Simply build it.
|
|
|
|
|
|
|
|
findutils
|
|
|
|
|
|
|
|
There is an expression for findutils-static. Simply build it.
|