[Mvapich-discuss] Avoid linking to libXNVCtrl.so

[Subramoni, Hari]

Hi, Ron.

Glad to hear that it worked for you.

Thanks for pointing us to the fact that these are not exposed on Spack. We will take care of it shortly.

Best,
Hari.

From: Rahaman, Ronald O <rrahaman6 at gatech.edu>
Sent: Monday, April 24, 2023 1:01 PM
To: Subramoni, Hari <subramoni.1 at osu.edu>; Announcement about MVAPICH2 (MPI over InfiniBand, RoCE, Omni-Path, iWARP and EFA) Libraries developed at NBCL/OSU <mvapich-discuss at lists.osu.edu>
Subject: Re: Avoid linking to libXNVCtrl.so

Hi Hari, Thanks! The extra flags (--disable-opencl --disable-gl --disable-nvml) solved my issue. I can see that MVAPICH2 was not configured to link to XNVCtrl on the dev node, and the OSU benchmark apps are working fine on the prod node. As
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
    Report Suspicious  <https://us-phishalarm-ewt.proofpoint.com/EWT/v1/KGKeukY!vwQd0oZND6YAhRdwHo7Fd6qJj2BONI0bhC_7C1hITdyOahSYlySkv_EWTddgJ6-UO6O0sqWKVrtqIZjABiLgfJT9p85e9W79c5mWrxwIWYHNADMQRxEqVoFaBYeNPifqtdzA02NE_MmxaA$>   ‌
ZjQcmQRYFpfptBannerEnd
Hi Hari,

Thanks!  The extra flags (--disable-opencl --disable-gl --disable-nvml) solved my issue.  I can see that MVAPICH2 was not configured to link to XNVCtrl on the dev node, and the OSU benchmark apps are working fine on the prod node.

As a follow-up, these flags aren’t exposed for the mvapich2 package in Spack.  I have enough working knowledge of Spack to update package.py for our site.  It would be nice to have this fix in the main Spack distribution.  Would y’all be able to contribute that?

Best,
Ron

--------
Ron Rahaman
Research Scientist II, Research Software Engineer
Partnership for an Advanced Computing Environment (PACE)
Georgia Institute of Technology

From: Subramoni, Hari <subramoni.1 at osu.edu<mailto:subramoni.1 at osu.edu>>
Date: Thursday, April 20, 2023 at 9:00 AM
To: Rahaman, Ronald O <rrahaman6 at gatech.edu<mailto:rrahaman6 at gatech.edu>>, Announcement about MVAPICH2 (MPI over InfiniBand, RoCE, Omni-Path, iWARP and EFA) Libraries developed at NBCL/OSU <mvapich-discuss at lists.osu.edu<mailto:mvapich-discuss at lists.osu.edu>>
Cc: Subramoni, Hari <subramoni.1 at osu.edu<mailto:subramoni.1 at osu.edu>>
Subject: RE: Avoid linking to libXNVCtrl.so
Hi, Ron.

Can you please add the following to the configure line and retry the build?

--disable-opencl --disable-gl --disable-nvml

Best,
Hari.

From: Mvapich-discuss <mvapich-discuss-bounces at lists.osu.edu<mailto:mvapich-discuss-bounces at lists.osu.edu>> On Behalf Of Rahaman, Ronald O via Mvapich-discuss
Sent: Thursday, April 20, 2023 9:18 AM
To: mvapich-discuss at lists.osu.edu<mailto:mvapich-discuss at lists.osu.edu>
Subject: [Mvapich-discuss] Avoid linking to libXNVCtrl.so

Hi all, I need to build MVAPICH2 on a dev server with a GPU; and then deploy it to a prod cluster where many nodes do not have GPUs. However, when I build on the dev server, MVAPICH2 is linked to the available libXNVCtrl. so. Thus on the GPU-less
Hi all,

I need to build MVAPICH2 on a dev server with a GPU; and then deploy it to a prod cluster where many nodes do not have GPUs.  However, when I build on the dev server, MVAPICH2 is linked to the available libXNVCtrl.so.  Thus on the GPU-less nodes on prod cluster, there are load-time errors since libXNVCtrl.so is not available.

Is there a way to configure MVAPICH so it will not link to libXNVCtrl.so?

I already have `--disable-cuda` set when I configure.  If I need to build and deploy a differently-configured hwloc, I can definitely manage that.

Many thanks,
Ron

--------
Ron Rahaman
Research Scientist II, Research Software Engineer
Partnership for an Advanced Computing Environment (PACE)
Georgia Institute of Technology
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osu.edu/pipermail/mvapich-discuss/attachments/20230424/b588b7f4/attachment-0007.html>