diff options
| author | Arnout Engelen <arnout@bzzt.net> | 2019-11-09 10:07:59 +0100 |
|---|---|---|
| committer | Arnout Engelen <arnout@bzzt.net> | 2019-11-09 10:10:47 +0100 |
| commit | 07c84f4de229cddd1abc87350bbe17a4725964b1 (patch) | |
| tree | dc052f44bb1fb26672568fb4d94207089569d6d9 /doc/stdenv | |
| parent | eebdaa936fb03ed8879ae74e2d7a24656d2d454d (diff) | |
| download | nixpkgs-07c84f4de229cddd1abc87350bbe17a4725964b1.tar nixpkgs-07c84f4de229cddd1abc87350bbe17a4725964b1.tar.gz nixpkgs-07c84f4de229cddd1abc87350bbe17a4725964b1.tar.bz2 nixpkgs-07c84f4de229cddd1abc87350bbe17a4725964b1.tar.lz nixpkgs-07c84f4de229cddd1abc87350bbe17a4725964b1.tar.xz nixpkgs-07c84f4de229cddd1abc87350bbe17a4725964b1.tar.zst nixpkgs-07c84f4de229cddd1abc87350bbe17a4725964b1.zip | |
documentation: drop double 'the'
Diffstat (limited to 'doc/stdenv')
| -rw-r--r-- | doc/stdenv/cross-compilation.xml | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/stdenv/cross-compilation.xml b/doc/stdenv/cross-compilation.xml index 93fe9095ce2..5476c9a4893 100644 --- a/doc/stdenv/cross-compilation.xml +++ b/doc/stdenv/cross-compilation.xml @@ -348,12 +348,12 @@ nix-build '<nixpkgs>' --arg crossSystem '{ config = "<arch>-<os&g </para> </listitem> </orderedlist> - In each stage, <varname>pkgsBuildHost</varname> refers the the previous stage, <varname>pkgsBuildBuild</varname> refers to the one before that, and <varname>pkgsHostTarget</varname> refers to the current one, and <varname>pkgsTargetTarget</varname> refers to the next one. When there is no previous or next stage, they instead refer to the current stage. Note how all the invariants regarding the mapping between dependency and depending packages' build host and target platforms are preserved. <varname>pkgsBuildTarget</varname> and <varname>pkgsHostHost</varname> are more complex in that the stage fitting the requirements isn't always a fixed chain of "prevs" and "nexts" away (modulo the "saturating" self-references at the ends). We just special case each instead. All the primary edges are implemented is in <filename>pkgs/stdenv/booter.nix</filename>, and secondarily aliases in <filename>pkgs/top-level/stage.nix</filename>. + In each stage, <varname>pkgsBuildHost</varname> refers to the previous stage, <varname>pkgsBuildBuild</varname> refers to the one before that, and <varname>pkgsHostTarget</varname> refers to the current one, and <varname>pkgsTargetTarget</varname> refers to the next one. When there is no previous or next stage, they instead refer to the current stage. Note how all the invariants regarding the mapping between dependency and depending packages' build host and target platforms are preserved. <varname>pkgsBuildTarget</varname> and <varname>pkgsHostHost</varname> are more complex in that the stage fitting the requirements isn't always a fixed chain of "prevs" and "nexts" away (modulo the "saturating" self-references at the ends). We just special case each instead. All the primary edges are implemented is in <filename>pkgs/stdenv/booter.nix</filename>, and secondarily aliases in <filename>pkgs/top-level/stage.nix</filename>. </para> <note> <para> - Note the native stages are bootstrapped in legacy ways that predate the current cross implementation. This is why the the bootstrapping stages leading up to the final stages are ignored inthe previous paragraph. + Note the native stages are bootstrapped in legacy ways that predate the current cross implementation. This is why the bootstrapping stages leading up to the final stages are ignored inthe previous paragraph. </para> </note> |