Charm++ parallel programming system

[Benjamin Welton <welton AT cs.wisc.edu>]

Hello All,

 

Recently when compiling and running the application ChaNGa built with dynamic linkage* to Charm++ (git rev: 6e41e5), I was running into a segfault in libconv-util.so involving libmpich-gnu. I am building Charm++ with the following build line:

 

>  ./build ChaNGa gni-crayxe-cuda hugepages --with-production -j8 --build-shared

 

During the build process, libconv-util.so would be created and would have a dynamic link to libmpich_gnu_49.so (included in the default module cray-mpich/7.4.0). I was able to resolve the segfault by unloading the module prior to compilation of Charm++ (resulting in libconv-util.so not being linked with libmpich and ChaNGa launching/running correctly).

 

I am wondering if libmpich was supposed to be linked at all with libconv-util.so. Since I am not building AMPI, I was a bit surprised to see this linked anywhere in this build. If libmpich was in fact supposed to be linked on this build and shouldn’t have been removed, what version(s) of cray-mpich (or another mpich library) are known to work with Charm++?  

 

Thanks for your time,

Ben

 

* I understand fully that building applications with dynamic linkage on Cray machines is generally not advised. There is a specific purpose/reason that I have modified the application ChaNGa to build dynamically instead of statically to Charm++.