> On Apr 25, 2018, at 8:16 AM, Michael Di Domenico
> wrote:
>
> On Mon, Apr 23, 2018 at 6:07 PM, r...@open-mpi.org wrote:
>> Looks like the problem is that you didn’t wind up with the external PMIx.
>> The component listed in your error is the internal PMIx one which shouldn’t
>> have built
On Mon, Apr 23, 2018 at 6:07 PM, r...@open-mpi.org wrote:
> Looks like the problem is that you didn’t wind up with the external PMIx. The
> component listed in your error is the internal PMIx one which shouldn’t have
> built given that configure line.
>
> Check your config.out and see what happe
Hi Gilles,
Yes, I did. It was ignored AFAICT.I did not look for the reason - only so
many hours in the day.
Regards,
Charlie
> On Apr 24, 2018, at 8:07 AM, wrote:
>
> Charles,
>
> have you tried to configure --with-pmix-libdir=/.../lib64 ?
>
> Cheers,
>
> Gilles
>
> - Origin
Charles,
have you tried to configure --with-pmix-libdir=/.../lib64 ?
Cheers,
Gilles
- Original Message -
> I’ll add that when building OpenMPI 3.0.0 with an external PMIx, I
found that the OpenMPI configure script only looks in “lib” for the the
pmix library but the pmix configure/bui
I’ll add that when building OpenMPI 3.0.0 with an external PMIx, I found that
the OpenMPI configure script only looks in “lib” for the the pmix library but
the pmix configure/build uses “lib64” (as it should on a 64-bit system) so the
configure script falls back to the internal PMIx. As Robert
Hi Michael
Looks like the problem is that you didn’t wind up with the external PMIx. The
component listed in your error is the internal PMIx one which shouldn’t have
built given that configure line.
Check your config.out and see what happened. Also, ensure that your
LD_LIBRARY_PATH is properly
