[Top][All Lists]

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

[bug#39588] (off-topic) double time-machine explanations

From: zimoun
Subject: [bug#39588] (off-topic) double time-machine explanations
Date: Wed, 21 Oct 2020 16:43:41 +0200

Dear Maurice,

Thank you for the tests.  Ouch!  I will try to give a deep look next
week...  even if it is maybe out of my skill.  Well, the v1.2 is
coming and it could be nice to have both MPI. :-)

On Mon, 19 Oct 2020 at 15:46, Maurice Brémond <> wrote:


> Note that it is ok with the raw mpich patch
> guix time-machine --commit=398ec3c1e265a3f89ed07987f33b264db82e4080 -- 
> time-machine --url= 
> --branch=add-mpich -- build mumps-openmpi --with-input=openmpi=mpich
> I tried a build with the same hwloc as the embedded commit 
> f7b08df258c2e7d04ca2035ddd55a1de91f806d4
> (the HEAD used for hwloc in mpich) but the result is the same:
> guix time-machine --commit=398ec3c1e265a3f89ed07987f33b264db82e4080 -- 
> time-machine --url= 
> --branch=test-mpich -- build mumps-openmpi --with-input=openmpi=mpich
> (the 2 steps time-machine needed is another question...)

The 2 "time-machine" are because the repo lags really behind master, I
guess.  You can cut to only one by using a channel file, something

--8<---------------cut here---------------start------------->8---
(list (channel
        (name 'guix)
        (url "";)
         (name ’yours)
         (url "";)))
--8<---------------cut here---------------end--------------->8---

and then "guix time-machine -C channels.scm -- build ..."


But yeah, that's another story. :-)

All the best,

reply via email to

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