[mvapich-discuss] install question

[Morin, Monique Marlene]

Hi,


Here is the configure line we are using on a GPU machine (both with the 2.3 and 2.2 tarballs):


./configure --prefix=${final_install_path} --with-device=ch3:mrail --with-rdma=gen2 --with-pm=slurm --with-pmi=pmi2 --with-slurm=/usr/bin --enable-cuda --with-cuda=${cuda_opt_path} --enable-romio --with-file-system=lustre+nfs+ufs --enable-g=dbg --enable-debuginfo --enable-shared --with-ch3-rank-bits=32

Any suggestions welcome....thanks!


________________________________
From: Subramoni, Hari <subramoni.1 at osu.edu>
Sent: Monday, August 27, 2018 10:13 PM
To: Morin, Monique Marlene; mvapich-discuss at cse.ohio-state.edu
Cc: Subramoni, Hari
Subject: RE: install question


Hi, Monique.



Apologies for the delay in getting back.



As you say, this error message comes from the CUDA library (host_config.h). Ideally, this should not have any dependency with the version of MVAPICH2 library you’re using. In order to debug this further, could you please let us know the configure command you are using for both MVAPICH2 2.3 and MVAPICH2 2.2?



Best Regards,

Hari.



From: mvapich-discuss-bounces at cse.ohio-state.edu On Behalf Of Morin, Monique Marlene
Sent: Saturday, August 25, 2018 12:41 AM
To: mvapich-discuss at cse.ohio-state.edu <mvapich-discuss at mailman.cse.ohio-state.edu>
Subject: [mvapich-discuss] install question



Hello,



I am writing to ask about something that seems different between the 2.3 vs 2.2 source tarball of MVAPICH when configuring with cudatoolkit.



If we install 2.3 using the Intel compiler version 18+ (and cudatoolkit 9.0 or 9.1) we get the following error, apparently generated by cudatoolkit (host.config):





"error: #error directive: -- unsupported ICC configuration! Only ICC 15.0, ICC 16.0, and ICC 17.0 on Linux x86_64 are supported!
  #error -- unsupported ICC configuration! Only ICC 15.0, ICC 16.0, and ICC 17.0 on Linux x86_64 are supported!"





However, with only changing back (all other versions the same) to 2.2 we are fine -- no error, and install completes and OSU BW benchmark works.



Wondering if perhaps there was a workaround in 2.2 that did not make it to 2.3 source tarball?



Has anyone else run into this?



Thanks!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.cse.ohio-state.edu/pipermail/mvapich-discuss/attachments/20180828/a6aded17/attachment.html>