summary refs log tree commit diff
path: root/doc/stdenv/cross-compilation.chapter.md
diff options
context:
space:
mode:
authorsternenseemann <0rpkxez4ksa01gb3typccl0i@systemli.org>2021-04-02 10:02:48 +0200
committersternenseemann <0rpkxez4ksa01gb3typccl0i@systemli.org>2021-04-02 10:03:00 +0200
commitcf8da7eabda0336a3be0329eb95bbe1feb24df52 (patch)
treee06c4431108b092c01899fcc41f388709e626021 /doc/stdenv/cross-compilation.chapter.md
parent9ac5c7df176fbe091ba5e508240b37d3e4ba6f37 (diff)
downloadnixpkgs-cf8da7eabda0336a3be0329eb95bbe1feb24df52.tar
nixpkgs-cf8da7eabda0336a3be0329eb95bbe1feb24df52.tar.gz
nixpkgs-cf8da7eabda0336a3be0329eb95bbe1feb24df52.tar.bz2
nixpkgs-cf8da7eabda0336a3be0329eb95bbe1feb24df52.tar.lz
nixpkgs-cf8da7eabda0336a3be0329eb95bbe1feb24df52.tar.xz
nixpkgs-cf8da7eabda0336a3be0329eb95bbe1feb24df52.tar.zst
nixpkgs-cf8da7eabda0336a3be0329eb95bbe1feb24df52.zip
doc/stdenv/cross: fix typo
Diffstat (limited to 'doc/stdenv/cross-compilation.chapter.md')
-rw-r--r--doc/stdenv/cross-compilation.chapter.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/stdenv/cross-compilation.chapter.md b/doc/stdenv/cross-compilation.chapter.md
index ee090c82114..96641426628 100644
--- a/doc/stdenv/cross-compilation.chapter.md
+++ b/doc/stdenv/cross-compilation.chapter.md
@@ -190,7 +190,7 @@ If one imagines the saturating self references at the end being replaced with in
 ```
 (native..., native, native, native, foreign, foreign, foreign...)
 ```
-On can then imagine any sequence of platforms such that there are bootstrap stages with their 3 platforms determined by "sliding a window" that is the 3 tuple through the sequence. This was the original model for bootstrapping. Without a target platform (assume a better world where all compilers are multi-target and all standard libraries are built in their own derivation), this is sufficient. Conversely if one wishes to cross compile "faster", with a "Canadian Cross" bootstrapping stage where `build != host != target`, more bootstrapping stages are needed since no sliding window provides the pesky `pkgsBuildTarget` package set since it skips the Canadian cross stage's "host".
+One can then imagine any sequence of platforms such that there are bootstrap stages with their 3 platforms determined by "sliding a window" that is the 3 tuple through the sequence. This was the original model for bootstrapping. Without a target platform (assume a better world where all compilers are multi-target and all standard libraries are built in their own derivation), this is sufficient. Conversely if one wishes to cross compile "faster", with a "Canadian Cross" bootstrapping stage where `build != host != target`, more bootstrapping stages are needed since no sliding window provides the pesky `pkgsBuildTarget` package set since it skips the Canadian cross stage's "host".
 
 
 ::: note