-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error during make: ‘MPI’ does not name a type #72
Comments
Hi, It seems as if the compiler picks up a version of the header file mpi.h which does not support the MPI C++ bindings. This could either be because the wrong mpi.h is included or that the MPI implementation on the HPC cluster does not support the C++ bindings. Could you perhaps bring this issue up with the support personel at your HPC site such that they could look into it? Also, which version of MPI is your HPC site using? |
Thank you for your quick response! There are different versions available there, but so far I have used 3.1.1 and 4.0.3. I have installed MUSIC on PCs with these versions of MPI and there the compilation went fine, so this seems not to be a version-related problem. |
Hello @mmohaghegh, I'm having the same issue! Did you manage to solve this? Best, |
It was an issue for one specific computing resource that I wanted to work with. Since I did not need the resource back then, I stopped researching it further and following instructions in this comment. Best, Mohammad |
C++ bindings in MPI are deprecated, see #27. |
Hi all,
I would like to install MUSIC on an HPC. Despite loading all necessary modules for compiling MUSIC, I get this error and many errors like this during make: ./music/data_map.hh:46:13: error: ‘MPI’ does not name a type
virtual MPI::Datatype type () = 0;
On my PC the compilation goes without any problem. I have tried with different versions of mpi on PC as well as on HPC, including 3.1.1 and 4.0.3, however I get the same error for all of the versions only on HPC.
Could someone help me on this issue?
Best,
Mohammad
The text was updated successfully, but these errors were encountered: