On Fri, Jul 24, 2020 at 2:00 PM Reuti wrote:
> There is OPAL_PREFIX to be set:
> https://www.open-mpi.org/faq/?category=building#installdirs
>
Thanks. I will experiment with the OPAL_PREFIX.
.. Lana (lana.de...@gmail.com)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Am 24.07.2020 um 18:55 schrieb Lana Deere via users:
> I have open-mpi 4.0.4 installed on my desktop and my small test programs are
> working.
>
> I would like to migrate the open-mpi to a cluster and run a larger program
> there. When moved,
Hi
Currently i am approaching a similar problem/workflow with spack and an AWS
S3 shared storage. Mounting the storage from a laptop gives you same layout
as on each node of my AWC EC2 cluster.
As others mentioned before: you still have to recompile your work, to take
advantage of the XEON class c
+1
In my experience moving software, especially something of the complexity of
(Open) MPI,
is much more troublesome (and often just useless frustration) and time
consuming than recompiling it.
Hardware, OS, kernel, libraries, etc, are unlikely to be compatible.
Gus Correa
On Fri, Jul 24, 2020 at 1
On 7/24/20 7:55 PM, Lana Deere via users wrote:
I have open-mpi 4.0.4 installed on my desktop and my small test programs
are working.
I would like to migrate the open-mpi to a cluster and run a larger
program there. When moved, the open-mpi installation is in a different
pathname than it was
While possible, it is highly unlikely that your desktop version is going to be
binary compatible with your cluster...
On Jul 24, 2020, at 9:55 AM, Lana Deere via users mailto:users@lists.open-mpi.org> > wrote:
I have open-mpi 4.0.4 installed on my desktop and my small test programs are
working.
I have open-mpi 4.0.4 installed on my desktop and my small test programs
are working.
I would like to migrate the open-mpi to a cluster and run a larger program
there. When moved, the open-mpi installation is in a different pathname
than it was on my desktop and it doesn't seem to work any longer
