Thanks for the replies. Very helpful. I thought that —with-libevent=/usr was
equivalent but better than —with-libevent=external but I was really just
shooting myself in the foot.
Changing the pmix, libevent, and hwloc config options to,
--with-pmix=/opt/pmix --with-libevent=external --with-hwloc=external
resulted in a working config and working libraries. One note - I _did_ have to
create a lib -> lib64 symlink in /opt/pmix so that is something the configure
script maintainers may want to take a look at. Doesn’t seem like that should
be necessary on a x86_64 platform.
Thanks again for setting me straight.
Charlie
> On Mar 7, 2018, at 7:08 PM, Gilles Gouaillardet
> <gilles.gouaillar...@gmail.com> wrote:
>
> Charles,
>
> First, you should really
>
> configure --with-libevent=external
>
> Then could you please describe the issue ?
> configure ? make ?
>
> if configure fails, please compress and attach your config.log so we
> can have a look
>
>
> Cheers,
>
> Gilles
>
> On Thu, Mar 8, 2018 at 9:02 AM, r...@open-mpi.org <r...@open-mpi.org> wrote:
>> So long as it is libevent-devel-2.0.22, you should be okay. You might want
>> to up PMIx to v1.2.5 as Slurm 16.05 should handle that okay. OMPI v3.0.0 has
>> PMIx 2.0 in it, but should be okay with 1.2.5 last I checked (but it has
>> been awhile and I can’t swear to it).
>>
>>
>>> On Mar 7, 2018, at 2:03 PM, Charles A Taylor <chas...@ufl.edu> wrote:
>>>
>>> Hi
>>>
>>> Distro: RHEL-7 (7.4)
>>> SLURM: 16.05.11
>>> PMIx: 1.1.5
>>>
>>> Trying to build OpenMPI 3.0.0 for our RHEL7 systems but running into what
>>> might be a configure script issue more than a real incompatibility problem.
>>> Configuring with the following,
>>>
>>> --with-slurm=/opt/slurm --with-pmix=/opt/pmix
>>> --with-external-libpmix=/opt/pmix/lib64 --with-libevent=/usr
>>>
>>> It seems happy enough with PMIx and there appears to be PMIx 1.x support.
>>> However, libevent is another issue and my take so far is that the EL7
>>> native libevent-devel-2.0.x is the crux of the problem. It doesn’t seem
>>> like the configure script expects that and I’m a little reluctant to start
>>> patching things together with symlinks or configure script changes.
>>>
>>> My real question is what is intended? Should this be working or was 3.0.0
>>> really intended for PMIx 2.x? I imagine we will go to PMIx 2.x with SLURM
>>> 17 but aren’t quite ready for that yet.
>>>
>>> Regards,
>>>
>>> Charlie Taylor
>>> UF Research Computing
>>>
>>>
>>> _______________________________________________
>>> users mailing list
>>> users@lists.open-mpi.org
>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.open-2Dmpi.org_mailman_listinfo_users&d=DwIGaQ&c=pZJPUDQ3SB9JplYbifm4nt2lEVG5pWx2KikqINpWlZM&r=HOtXciFqK5GlgIgLAxthUQ&m=2uvuXdSIFiI-RGnA80gNIcK6B7zzhsvhKg9XAG2KplQ&s=6Ai2bxZZkFjhLn00ADhGjVs9z-1J93avnmK1_OtFqGw&e=
>>
>> _______________________________________________
>> users mailing list
>> users@lists.open-mpi.org
>> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.open-2Dmpi.org_mailman_listinfo_users&d=DwIGaQ&c=pZJPUDQ3SB9JplYbifm4nt2lEVG5pWx2KikqINpWlZM&r=HOtXciFqK5GlgIgLAxthUQ&m=2uvuXdSIFiI-RGnA80gNIcK6B7zzhsvhKg9XAG2KplQ&s=6Ai2bxZZkFjhLn00ADhGjVs9z-1J93avnmK1_OtFqGw&e=
> _______________________________________________
> users mailing list
> users@lists.open-mpi.org
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.open-2Dmpi.org_mailman_listinfo_users&d=DwIGaQ&c=pZJPUDQ3SB9JplYbifm4nt2lEVG5pWx2KikqINpWlZM&r=HOtXciFqK5GlgIgLAxthUQ&m=2uvuXdSIFiI-RGnA80gNIcK6B7zzhsvhKg9XAG2KplQ&s=6Ai2bxZZkFjhLn00ADhGjVs9z-1J93avnmK1_OtFqGw&e=
_______________________________________________
users mailing list
users@lists.open-mpi.org
https://lists.open-mpi.org/mailman/listinfo/users
