unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: "Maurice Brémond" <Maurice.Bremond@inria.fr>
Cc: "Ludovic Courtès" <ludo@gnu.org>, 39588@debbugs.gnu.org
Subject: [bug#39588] gnu: Add mpich, scalapack-mpich, mumps-mpich, pt-scotch-mpich, python-mpi4py-mpich
Date: Tue, 18 Feb 2020 19:22:17 +0100	[thread overview]
Message-ID: <CAJ3okZ0wT_LxDcZ1LvyKN9-_QDUO9i+U_43Uhjdma5gAeWg=0g@mail.gmail.com> (raw)
In-Reply-To: <87k14j6amk.fsf@inria.fr>

Hi Maurice,

On Tue, 18 Feb 2020 at 18:58, Maurice Brémond <Maurice.Bremond@inria.fr> wrote:

> If I understand, in this case, the usage of --with-input is
> possible because implicit packages are very likely to not use mpi ?

Maybe I miss the issue. I have not look at mumps and related since... years. :-)
(Neither your patches. :-D)

If mumps depends explicitly on openmpi, then '--with-inputs' can
rewrite the direct dependencies, by providing say mpich instead of
openmpi.
If petsc* depends explicitly on openmpi and on mumps (which depends
explicitly on openmpi too), then '--with-inputs=openmpi=mpich'  will
*only* rewrite the dependency of petsc but not of mumps. So it ends
with petsc compiled with mpich and mumps with openmpi.

Still considering this (fictive) example, where:
 - petsc depends on openmpi(1) and mumps
 - mumps depends on openmpi(2)
The openmpi(2) is an implicit dependency for petsc and '--with-inputs'
does not work.

*because I know better PETSc than Scotch. ;-)



> You can try with my original patch just a transformation of
> mumps-openmpi into mumps-mpich:
>
> guix time-machine --url=https://gitlab.inria.fr/bremond/guix.git \
>   --branch=add-mpich -- \
>   environment -K --pure --ad-hoc mumps-openmpi \
>   --with-input=mpi=mpich --with-input=openmpi=mpich --
>
> This works for me, I can use a similar command to compile and execute a
> program which uses mumps and I can see with ldd that mpich is used.
>
> Then with the current mpich patch on savannah master:
>
> guix time-machine --commit=c70261bfb993cebc23cd80042de3f52a8b7932a4 -- \
>   environment -K --pure --ad-hoc mumps-openmpi \
>   --with-input=mpi=mpich --with-input=openmpi=mpich --
>
> This fails on my machine for the pt-scotch check (there is the same
> error with scalapack check)

Are 'pt-scotch' and 'scalapack' compiled with 'mpich' or 'openmpi'?

Because maybe "mumps-openmpi --with-input=openmpi=mpich" compiles
'mumps' using 'mpich' as MPI but compile 'pt-scotch' or 'scalapack'
with the default implementation which seems 'openmpi'.


Thank you for your work.

All the best,
simon

  reply	other threads:[~2020-02-18 18:23 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
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 [this message]
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='CAJ3okZ0wT_LxDcZ1LvyKN9-_QDUO9i+U_43Uhjdma5gAeWg=0g@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).