From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: "Maurice Brémond" <Maurice.Bremond@inria.fr>, 39588@debbugs.gnu.org
Subject: [bug#39588] gnu: Add mpich, scalapack-mpich, mumps-mpich, pt-scotch-mpich, python-mpi4py-mpich
Date: Fri, 16 Oct 2020 13:46:16 +0200 [thread overview]
Message-ID: <CAJ3okZ1hnYkzwJ88=k6OvJ3TdU9uU_+DPFC-AqBDCDuaJc1J_g@mail.gmail.com> (raw)
In-Reply-To: <87o8l28qjh.fsf@gnu.org>
Dear,
On Fri, 16 Oct 2020 at 11:32, Ludovic Courtès <ludo@gnu.org> wrote:
> Thanks for staying on top of things! :-)
I have been a bit upset by recent discussions on French's HPC mailing
list about "modulefiles are awesome" ---- well I am sure they are
applying variant of "prêcher le faux pour savoir le vrai" [1]. :-)
1: <https://meta.wikimedia.org/wiki/Cunningham%27s_Law>
> > On Thu, 20 Feb 2020 at 10:08, Ludovic Courtès <ludo@gnu.org> wrote:
> > Now the “#:deep?” exists, does it make sense to implement this
> > “package-with-mpich” procedure? It could be helpful for HPC people,
> > isn’t?
>
> Or does ‘--with-input=openmpi=mpich’ fit the bill now?
I do not have an MPI infrastructure or enough CPU power to rebuild a
lot at hand to fully test it. If one of you can try on right infra
and report, it could be awesome.
BTW, it should work only if MPICH does not require extra phases or
environment variables.
All the best,
simon
next prev parent reply other threads:[~2020-10-16 11:47 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-13 10:44 [bug#39588] gnu: Add mpich, scalapack-mpich, mumps-mpich, pt-scotch-mpich, python-mpi4py-mpich Maurice Brémond
2020-02-17 17:26 ` Ludovic Courtès
2020-02-17 18:20 ` zimoun
2020-02-20 9:08 ` Ludovic Courtès
2020-02-20 10:23 ` zimoun
2020-02-21 8:03 ` Ludovic Courtès
2020-02-21 8:40 ` zimoun
2020-02-25 16:41 ` zimoun
2020-10-15 19:50 ` zimoun
2020-10-16 9:32 ` Ludovic Courtès
2020-10-16 11:46 ` zimoun [this message]
2020-10-19 13:46 ` Maurice Brémond
2020-10-20 20:55 ` Ludovic Courtès
2020-10-23 9:33 ` Maurice Brémond
2020-10-23 15:26 ` Ludovic Courtès
2020-10-23 17:04 ` Maurice Brémond
2020-11-02 14:02 ` bug#39588: " Ludovic Courtès
2020-10-21 14:43 ` [bug#39588] (off-topic) double time-machine explanations zimoun
2020-10-23 8:41 ` Maurice Brémond
2020-02-18 17:58 ` [bug#39588] gnu: Add mpich, scalapack-mpich, mumps-mpich, pt-scotch-mpich, python-mpi4py-mpich Maurice Brémond
2020-02-18 18:22 ` zimoun
2020-02-19 11:45 ` Maurice Brémond
2020-02-19 12:11 ` zimoun
2020-02-19 13:34 ` zimoun
2020-02-21 9:01 ` Maurice Brémond
2020-02-20 9:38 ` Ludovic Courtès
2020-02-21 8:46 ` Maurice Brémond
2020-02-21 11:32 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJ3okZ1hnYkzwJ88=k6OvJ3TdU9uU_+DPFC-AqBDCDuaJc1J_g@mail.gmail.com' \
--to=zimon.toutoune@gmail.com \
--cc=39588@debbugs.gnu.org \
--cc=Maurice.Bremond@inria.fr \
--cc=ludo@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).