Angel, Infiniband detection likely fails before checking expanded verbs. Please compress and post the full configure output
Cheers, Gilles On Fri, Feb 18, 2022 at 12:02 AM Angel de Vicente via users < users@lists.open-mpi.org> wrote: > Hi, > > I'm trying to compile the latest OpenMPI version with Infiniband support > in our local cluster, but didn't get very far (since I'm installing this > via Spack, I also asked in their support group). > > I'm doing the installation via Spack, which is issuing the following > .configure step (see the options given for --with-knem, --with-hcoll and > --with-mxm): > > ,---- > | configure' > | > '--prefix=/storage/projects/can30/angelv/spack/opt/spack/linux-sles12-sandybridge/gcc-9.3.0/openmpi-4.1.1-jsvbusyjgthr2d6oyny5klt62gm6ma2u' > | '--enable-shared' '--disable-silent-rules' '--disable-builtin-atomics' > | '--enable-static' '--without-pmi' > | > '--with-zlib=/storage/projects/can30/angelv/spack/opt/spack/linux-sles12-sandybridge/gcc-9.3.0/zlib-1.2.11-hrstx5ffrg4f4k3xc2anyxed3mmgdcoz' > | '--enable-mpi1-compatibility' '--with-knem=/opt/knem-1.1.2.90mlnx2' > | '--with-hcoll=/opt/mellanox/hcoll' '--without-psm' '--without-ofi' > | '--without-cma' '--without-ucx' '--without-fca' > | '--with-mxm=/opt/mellanox/mxm' '--without-verbs' '--without-xpmem' > | '--without-psm2' '--without-alps' '--without-lsf' '--without-sge' > | '--without-slurm' '--without-tm' '--without-loadleveler' > | '--disable-memchecker' > | > '--with-libevent=/storage/projects/can30/angelv/spack/opt/spack/linux-sles12-sandybridge/gcc-9.3.0/libevent-2.1.12-yd5l4tjmnigv6dqlv5afpn4zc6ekdchc' > | > '--with-hwloc=/storage/projects/can30/angelv/spack/opt/spack/linux-sles12-sandybridge/gcc-9.3.0/hwloc-2.6.0-bfnt4g3givflydpe5d2iglyupgbzxbfn' > | '--disable-java' '--disable-mpi-java' '--without-cuda' > | '--enable-wrapper-rpath' '--disable-wrapper-runpath' '--disable-mpi-cxx' > | '--disable-cxx-exceptions' > | > '--with-wrapper-ldflags=-Wl,-rpath,/storage/projects/can30/angelv/spack/opt/spack/linux-sles12-sandybridge/gcc-7.2.0/gcc-9.3.0-ghr2jekwusoa4zip36xsa3okgp3bylqm/lib/gcc/x86_64-pc-linux-gnu/9.3.0 > | > -Wl,-rpath,/storage/projects/can30/angelv/spack/opt/spack/linux-sles12-sandybridge/gcc-7.2.0/gcc-9.3.0-ghr2jekwusoa4zip36xsa3okgp3bylqm/lib64' > `---- > > Later on in the configuration phase I see: > > ,---- > | --- MCA component btl:openib (m4 configuration macro) > | checking for MCA component btl:openib compile mode... static > | checking whether expanded verbs are available... yes > | checking whether IBV_EXP_ATOMIC_HCA_REPLY_BE is declared... yes > | checking whether IBV_EXP_QP_CREATE_ATOMIC_BE_REPLY is declared... yes > | checking whether ibv_exp_create_qp is declared... yes > | checking whether ibv_exp_query_device is declared... yes > | checking whether IBV_EXP_QP_INIT_ATTR_ATOMICS_ARG is declared... yes > | checking for struct ibv_exp_device_attr.ext_atom... yes > | checking for struct ibv_exp_device_attr.exp_atomic_cap... yes > | checking if MCA component btl:openib can compile... no > `---- > > This is the first time I try to compile OpenMPI this way, and I get a > bit confused with what each bit is doing, but it looks like it goes > through the moves to get the btl:openib built, but then for some reason > it cannot compile it. > > Any suggestions/pointers? > > Many thanks, > -- > Ángel de Vicente > > Tel.: +34 922 605 747 > Web.: http://research.iac.es/proyecto/polmag/ > > --------------------------------------------------------------------------------------------- > AVISO LEGAL: Este mensaje puede contener información confidencial y/o > privilegiada. Si usted no es el destinatario final del mismo o lo ha > recibido por error, por favor notifíquelo al remitente inmediatamente. > Cualquier uso no autorizadas del contenido de este mensaje está > estrictamente prohibida. Más información en: > https://www.iac.es/es/responsabilidad-legal > DISCLAIMER: This message may contain confidential and / or privileged > information. If you are not the final recipient or have received it in > error, please notify the sender immediately. Any unauthorized use of the > content of this message is strictly prohibited. More information: > https://www.iac.es/en/disclaimer >
