-
Notifications
You must be signed in to change notification settings - Fork 102
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
--with-mpi #1
Comments
Sounds good to me. Please go ahead and implement it. |
RESOLVED: Now with --with-mpi= on its own means "define -DMPI_COMMS and build for MPI using the MPI in ". --with-qmp= together with --with-mpi= means: "define -DQMP_COMMS and build for QMP, but using the mpicc, mpirun etc in " |
That's more intuitive, better solution. Thanks |
Agreed. I like this. |
ckallidonis
pushed a commit
to ckallidonis/quda
that referenced
this issue
May 8, 2018
Enables ARPACK, restructures some code.
ckallidonis
pushed a commit
to ckallidonis/quda
that referenced
this issue
Dec 30, 2019
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi Guys,
--with-mpi on the configure script appears to be overloaded. I originally specified it to point to the location of the MPI distro which was used to compile QMP programs. It has now been overloaded to also define -DUSE_MPI (to select MPI vs QMP comms harness). This is bad because it is natural to have --with-qmp= --with-mpi= set together for a normal QMP build, and this will add -DQMP_COMMS and -DMPI_COMMS on the command line.
We should find a way around. How about
--with-qmp= sets -DQMP_COMMS
--with-mpi= sets -DMPI_COMMS
--with-mpihome= sets MPI_HOME, but not -DMPI_COMMS
Thoughts?
The text was updated successfully, but these errors were encountered: