Crud, it sounds like here our applications often do not have their lmod module environment set up to match what their application was built against. So it looks like I'll need to set things up the hard way. Chris On 3/5/20 2:37 PM, Christopher J. Morrone wrote:
Oh, great! Hopefully I can exploit lmod in the same way. Thanks!
Chris
On 3/5/20 1:56 PM, Curry, Matthew Leon wrote:
Hi Chris,
Our ThunderX2 systems have openmpi3, openmpi4, and hpempi. The general strategy is as you say: We build Darshan's runtime with each MPI (and some recent version of the GNU compiler). In the end, we have created one darshan-runtime package for each MPI, and a single darshan-util package that includes the analysis tools.
Our lmod modules for our MPIs change the MODULEPATH to point to software compiled for that MPI. When we do a "module swap" to change MPIs, lmod is smart enough to change out the darshan module for one that is in the new MODULEPATH. We manage LD_PRELOAD in the Darshan module files, so it gets updated automatically.
Matthew
-----Original Message----- From: Darshan-users <[email protected]> On Behalf Of Christopher J. Morrone Sent: Thursday, March 5, 2020 2:48 PM To: [email protected] Subject: [EXTERNAL] [Darshan-users] Multiple MPI libraries on one system?
Has anyone out there dealt with using darshan on a system that has multiple MPI libraries installed? Since various MPIs are not necessarily ABI compatible, I presume that I'll need multiple builds of darshan, and a mechanism to select the correct darshan LD_PRELOAD based on which MPI any particular application is using.
Any tips for making this easier?
Chris _______________________________________________ Darshan-users mailing list [email protected] https://lists.mcs.anl.gov/mailman/listinfo/darshan-users .
.