summary refs log tree commit diff
path: root/doc/guix.texi
diff options
context:
space:
mode:
authorJan Nieuwenhuizen <janneke@gnu.org>2018-11-20 21:02:53 +0100
committerJan Nieuwenhuizen <janneke@gnu.org>2018-11-24 08:18:31 +0100
commit3d3daf7fa1794c64914ed53e51838a41d9b7adc4 (patch)
tree06c1bd57aff9d85b39215ad78b549e0a9d937a96 /doc/guix.texi
parentda91723cc5bba433f59ac40ee669d97e4cbc0e45 (diff)
downloadguix-3d3daf7fa1794c64914ed53e51838a41d9b7adc4.tar.gz
doc: Update for bootstrap-mescc-tools change.
* doc/guix.texi (Reduced Binary Seed Bootstrap): Update for
bootstrap-mescc-tools change.
* doc/images/gcc-mesboot-bag-graph.dot: Regenerate.
Diffstat (limited to 'doc/guix.texi')
-rw-r--r--doc/guix.texi23
1 files changed, 11 insertions, 12 deletions
diff --git a/doc/guix.texi b/doc/guix.texi
index 5ab42d121c..a957930d37 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -23930,13 +23930,12 @@ to use that term for what we do now.}.
 
 The Reduced Binary Seed bootstrap removes the most critical tools---from a
 trust perspective---from the bootstrap binaries: GCC, Binutils and the GNU C
-Library are replaced by: @code{mescc-tools-seed} (a tiny assembler and linker)
-@code{bootstrap-mes} (a small Scheme Interpreter and a C compiler written in
-Scheme and the Mes C Library, built for TinyCC and for GCC).  Using these new
-binary seeds and a new set of
+Library are replaced by: @code{bootstrap-mescc-tools} (a tiny assembler and
+linker) and @code{bootstrap-mes} (a small Scheme Interpreter and a C compiler
+written in Scheme and the Mes C Library, built for TinyCC and for GCC).  Using
+these new binary seeds and a new set of
 @c
 packages@footnote{@c
-mescc-tools-boot,
 nyacc-boot,
 mes-boot,
 tcc-boot0,
@@ -24030,8 +24029,8 @@ corresponds to the @code{#:modules} argument of
 
 Finally, the various tarballs are unpacked by the derivations
 @code{gcc-bootstrap-0.drv}, @code{glibc-bootstrap-0.drv}, or
-@code{bootstrap-mes-0.drv} and @code{mescc-tools-boot-0.drv}, at which point
-we have a working C tool chain.
+@code{bootstrap-mes-0.drv} and @code{bootstrap-mescc-tools-0.drv}, at which
+point we have a working C tool chain.
 
 @unnumberedsubsec Building the Build Tools
 
@@ -24096,11 +24095,11 @@ those rarely need to be updated.  Nevertheless, it is useful to have an
 automated way to produce them, should an update occur, and this is what
 the @code{(gnu packages make-bootstrap)} module provides.
 
-The following command builds the tarballs containing the bootstrap
-binaries (Binutils, GCC, glibc, for the traditional bootstrap and
-linux-libre-headers, mescc-tools-seed, bootstrap-mes for the Reduced
-Binary Seed bootstrap, and Guile, and a tarball containing a mixture
-of Coreutils and other basic command-line tools):
+The following command builds the tarballs containing the bootstrap binaries
+(Binutils, GCC, glibc, for the traditional bootstrap and linux-libre-headers,
+bootstrap-mescc-tools, bootstrap-mes for the Reduced Binary Seed bootstrap,
+and Guile, and a tarball containing a mixture of Coreutils and other basic
+command-line tools):
 
 @example
 guix build bootstrap-tarballs