Sajid,
I believe this is a Spack issue and Open MPI cannot do anything about it.
(long story short, `module load openmpi-xyz` does not set the
environment for the (spack) external `xpmem` library.
I updated the spack issue with some potential workarounds you might
want to give a try.
Cheers,
Gilles
On Sat, Jan 9, 2021 at 8:40 AM Sajid Ali via users
wrote:
>
> Hi OpenMPI-community,
>
> This is a cross post from the following spack issue :
> https://github.com/spack/spack/issues/20756
>
> In brief, when I install openmpi@4.1.0 with ucx and xpmem fabrics, the
> behaviour of the compiler wrappers (mpicc) seems to depend upon the method by
> which it is loaded into the user environment. When loaded by `spack load`,
> the compiler wrappers successfully compiler a test program. However, if the
> same compiler wrappers are loaded via `module load` or as part of a spack
> environment, they fail. What could possibly cause this inconsistency ?
>
> The build logs and the output of opmi_info are available here
> (https://we.tl/t-CaiOt7OefS) should it be of any help.
>
> Thank You,
> Sajid Ali (he/him) | PhD Candidate
> Applied Physics
> Northwestern University
> s-sajid-ali.github.io
