-
Notifications
You must be signed in to change notification settings - Fork 1
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
Not able to build with MPI and/or OpenMP #4
Comments
I'm unable to recreate this error. It looks like there is an issue with cmake finding MPI. You might need to specify the path to the MPI build and ensure the correct MPI is called in CMake is installed. |
I also am having trouble installing on Ubuntu. My error is that it just can't find
in the |
I tried again on Manjaro linux (essentialy Arch), and got a different MPI-based error:
Again, this happens whether or not I switch on MPI in the This is with |
With recent changes in the repository, I also get the errors @steven-murray mentions. I'm using ubuntu and gcc14, and tried with both openmpi 5 and 4.1 |
Can you try again? CMake is finding my mpi. I added lines to help cmake find the users mpi in the CMakeLists.txt. Are you using openmpi or mpich?
Does adding the mpi build location to you path help?
export PATH="/pathTo/open-mpi/bin:$PATH"
export CPATH="/pathTo/open-mpi/include:$CPATH"
export LIBRARY_PATH="/pathTo/open-mpi/lib:$LIBRARY_PATH"
export LD_LIBRARY_PATH="/pathTo/open-mpi/lib:$LD_LIBRARY_PATH"
…________________________________
From: M. Guadalupe Barrios Sazo ***@***.***>
Sent: Wednesday, July 10, 2024 9:49 AM
To: lanl/nuDustC ***@***.***>
Cc: Stangl, Sarah Marie ***@***.***>; Comment ***@***.***>
Subject: [EXTERNAL] Re: [lanl/nuDustC] Not able to build with MPI and/or OpenMP (Issue #4)
With recent changes in the repository, I also get the errors @steven-murray<https://urldefense.com/v3/__https://github.com/steven-murray__;!!Bt8fGhp8LhKGRg!FPO1qHVcXTJRljWn_QnfzmPHaTWGcuDul9bPFvHJDVQ5nTQa3cHL8EGj9oCM3QHObQeKpfUGOmlyM-qJAFGWdHdU4mc$> mentions. I'm using ubuntu and gcc14, and tried with both openmpi 5 and 4.1
—
Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https://github.com/lanl/nuDustC/issues/4*issuecomment-2220886667__;Iw!!Bt8fGhp8LhKGRg!FPO1qHVcXTJRljWn_QnfzmPHaTWGcuDul9bPFvHJDVQ5nTQa3cHL8EGj9oCM3QHObQeKpfUGOmlyM-qJAFGWe8yTx_U$>, or unsubscribe<https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AJTQOWV77CBCY43BK7GV6XDZLVJYNAVCNFSM6AAAAABHZ5OPZSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRQHA4DMNRWG4__;!!Bt8fGhp8LhKGRg!FPO1qHVcXTJRljWn_QnfzmPHaTWGcuDul9bPFvHJDVQ5nTQa3cHL8EGj9oCM3QHObQeKpfUGOmlyM-qJAFGW34hk6SY$>.
You are receiving this because you commented.Message ID: ***@***.***>
|
I just tried again "cmake -DNUDUSTC_ENABLE_MPI=ON" to make sure that MPI is enabled. The output I get is
So MPI is found, as shown by the recent message you added for that purpose. Also, looking at the CMakeCache.txt in the build directory I can see However the original issue message remains in the output. As I said originally I suspect the problem is with the quotes around |
Okay, I've removed the quotes.
…________________________________
From: M. Guadalupe Barrios Sazo ***@***.***>
Sent: Thursday, July 11, 2024 1:08 AM
To: lanl/nuDustC ***@***.***>
Cc: Stangl, Sarah Marie ***@***.***>; Comment ***@***.***>
Subject: [EXTERNAL] Re: [lanl/nuDustC] Not able to build with MPI and/or OpenMP (Issue #4)
I just tried again "cmake -DNUDUSTC_ENABLE_MPI=ON" to make sure that MPI is enabled. The output I get is
MPI Found
-- Configuring done
CMake Error at CMakeLists.txt:91 (target_link_libraries):
Target "nudustc++" links to:
"MPI::MPI_CXX"
but the target was not found. Possible reasons include:
* There is a typo in the target name.
* A find_package call is missing for an IMPORTED target.
* An ALIAS target is missing.
So MPI is found, as shown by the recent message you added for that purpose. Also, looking at the CMakeCache.txt in the build directory I can see MPI_mpi_LIBRARY:FILEPATH=/home/mgbarrioss/miniforge3/envs/joss_nuDustc_3/lib/libmpi.so
However the original issue message remains in the output.
As I said originally I suspect the problem is with the quotes around MPI::MPI_CXX in line 99 of CMakeLists.txt. If I remove those quotes, the build process finishes.
—
Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https://github.com/lanl/nuDustC/issues/4*issuecomment-2222195665__;Iw!!Bt8fGhp8LhKGRg!BSh0fVxQQt8ZZWGJuRSbvwxOFqe8h7ICq6CUsPRaZuMQ5ELiAqzUsGWkqlVx7V8Optrh3tPZZkPvpPmBqDyrzKlBuGo$>, or unsubscribe<https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AJTQOWRT7U4XBYP6FTGNYULZLYVPXAVCNFSM6AAAAABHZ5OPZSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRSGE4TKNRWGU__;!!Bt8fGhp8LhKGRg!BSh0fVxQQt8ZZWGJuRSbvwxOFqe8h7ICq6CUsPRaZuMQ5ELiAqzUsGWkqlVx7V8Optrh3tPZZkPvpPmBqDyrgEHN6LM$>.
You are receiving this because you commented.Message ID: ***@***.***>
|
Hi! This issue is also related to the JOSS review openjournals/joss-reviews#6637
Thank you for the description provided for installation, although I was able to build nuDustC serially, when trying to build with
NUDUSTC_ENABLE_MPI=ON
, I get the following error :I get an analogous error when using
NUDUSTC_ENABLE_OPENMP=ON
I tried both using cmake 3.29 and cmake 3.23.3, but it looks like the quotes inside the generator$<${with_mpi}:"MPI::MPI_CXX">
inCMakeLists.txt
might be causing an issue. CMake seems to find the path to the MPI relevant paths, so I'm not sure that is the problem.The text was updated successfully, but these errors were encountered: