[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

17/45: reppar: Remove empty figure.

From: Ludovic Courtès
Subject: 17/45: reppar: Remove empty figure.
Date: Tue, 09 Jun 2015 12:37:04 +0000

civodul pushed a commit to branch master
in repository maintenance.

commit eeec357f9b01819c30bda0be4e83f729d601f142
Author: Ludovic Courtès <address@hidden>
Date:   Sun May 31 13:16:28 2015 +0200

    reppar: Remove empty figure.
 doc/reppar-2015/reproducible-hpc.skb |   18 +++++++-----------
 1 files changed, 7 insertions(+), 11 deletions(-)

diff --git a/doc/reppar-2015/reproducible-hpc.skb 
index 8b9c8c2..6557e6e 100644
--- a/doc/reppar-2015/reproducible-hpc.skb
+++ b/doc/reppar-2015/reproducible-hpc.skb
@@ -30,14 +30,18 @@
              (guix hash) (guix base32)
              ((guix serialization) #:select (write-file))
-             (gnu packages))
+             (gnu packages)
+             ((gnu packages base) #:select (canonical-package glibc)))
-(define-values (%openmpi-path %openmpi-hash)
+(define-values (%glibc-path %openmpi-path %openmpi-hash)
   ;; Here we connect to the Guix build daemon to get information about
   ;; the software environment we are talking about.
   (guix:with-store store
     (let ((drv (package-derivation store openmpi)))
+        (derivation->output-path
+          (package-derivation store (canonical-package glibc)))
         ;; Compute the /gnu/store file name of our Open MPI.
         (derivation->output-path drv)
@@ -286,19 +290,11 @@ Although it is not perfect as we will see in ,(numref 
:text [Section]
 :ident "limitations"), this technique gives us confidence that build
 processes can be viewed as pure functions, with reproducible results.])
-      (figure
-        :legend [Invocation of the ,(tt [guix build]) command returning
-        the resulting file name in the store.]
-        :ident "fig-build"
-        ;;(include-latex "fig-build.tex")
-         (bold [FIXME: imagine a figure here]))
       (p [Each build process produces one or more files in directories
 stored in a common place called ,(emph [the store]), typically the ,(tt
 [/gnu/store]) directory.  Each file in ,(tt [/gnu/store]) has a name
 that includes a hash of all the inputs of the build process that led to
-it, as shown in ,(numref :text [Figure] :ident "fig-build").  By ``all
+it, such as ,(tt %glibc-path).  By ``all
 the inputs'', we really mean all of them: this includes of course
 compilers and libraries (including the C library), but also build
 scripts and environment variable values.  And this is recursive, the

reply via email to

[Prev in Thread] Current Thread [Next in Thread]