Where communities thrive

Join over 1.5M+ people
Join over 100K+ communities
Free without limits
Create your own community

Explore more communities

elemental/chat

People

Repo info

Activity

Dec 17 2021 09:42

JBlaschke opened #5
Jul 25 2021 14:53

PierreMarchand20 closed #255
Apr 09 2021 01:34

tldahlgren commented #254
May 02 2020 14:21

ernstbrunr51 commented #278
Apr 29 2020 20:49

yurivict opened #278
Apr 24 2020 18:55

ernstbrunr51 closed #277
Apr 24 2020 18:55

ernstbrunr51 commented #277
Apr 24 2020 18:04

poulson commented #277
Apr 24 2020 10:34

ernstbrunr51 opened #277
May 14 2019 01:33

poulson closed #276
May 14 2019 01:33

poulson commented #276
May 14 2019 01:30

poulson on master

Update README.md (compare)
May 14 2019 01:24

poulson on master

added logo (compare)
May 10 2019 21:37

jedbrown commented #276
May 10 2019 21:25

poulson commented #276
May 10 2019 21:21

jedbrown commented #276
May 10 2019 17:08

poulson commented #276
May 10 2019 17:03

tesch1 opened #276
Apr 10 2019 13:18

JM1 commented #275
Apr 10 2019 13:16

JM1 synchronize #275

Ryan H. Lewis

@rhl-

I'm not sure why.

Jeff Hammond

@jeffhammond

i'd love any help anyone can give me w.r.t. elemental/Elemental#185. CMake is completely unhelpful.

Ryan H. Lewis

@rhl-

@jeffhammond reading it now ..

@jeffhammond: i am hoping for us to move up to C++14.. haha

you need to look at the internals of: cmake/detect/MPI.cmake

Jeff Hammond

@jeffhammond

look at http://en.cppreference.com/w/cpp/compiler_support. three compilers support C++14 right now and one of them requires Windows

Ryan H. Lewis

@rhl-

aren't the other two gcc and clang?

Jeff Hammond

@jeffhammond

yes, they are, but moving to C++14 right now would be a clear statement that Elemental is not interested in supporting any HPC vendor compiler

Ryan H. Lewis

@rhl-

@jeffhammond sure. I agree we wouldn't want that..

Jeff Hammond

@jeffhammond

and there is at least one downstream ISV that must use Intel compilers.

Ryan H. Lewis

@rhl-

@jeffhammond can I replicated without a cray compiler?

Jeff Hammond

@jeffhammond

you might be able to replicate without the Cray compiler itself, but i think this is specific to the Cray programming environment wrappers

i can get you a NERSC account in a day if you want to fight with this, but i'd prefer that you invent a time machine and kill whatever person created CMake ;-)

Ryan H. Lewis

@rhl-

haha. I used to have a NERSC account. It might still be active..

Jeff Hammond

@jeffhammond

so there is no CMake log for the mpi.h faiure

it's ridiculous that it tells me to look in C++ detection output, which is unrelated

i set -DMPI_C_INCLUDE_PATH=$CRAY_MPICH_DIR/include

is that not correct?

Ryan H. Lewis

@rhl-

I'm not 100% sure, but, that doesn't seem right.

Ah, I bet its failing right here: find_package(MPI)

Jeff Hammond

@jeffhammond

yes it tells me CMake Error at cmake/detect/MPI.cmake:69 (message):
Could not find mpi.h
Call Stack (most recent call first):
CMakeLists.txt:361 (include)

and then "See also "/global/homes/j/jhammond/ELEMENTAL/git/build-cray/CMakeFiles/CMakeOutput.log"."

Ryan H. Lewis

@rhl-

Have you read: https://cmake.org/cmake/help/v3.0/module/FindMPI.html

can you add message ("MPI_FOUND=${MPI_FOUND}) just below find_package or something

Jeff Hammond

@jeffhammond

not until just now but you can see on the ticket what options i set

Ryan H. Lewis

@rhl-

@jeffhammond according to the docs you need to set MPI_C_LIBRARIES to the list of things to link against.

However, this is likely unrelated to the actual failure.

Jeff Hammond

@jeffhammond

cc is equivalent to mpicc on other platforms

no lib or inc options should be required ever

Ryan H. Lewis

@rhl-

well, the documentation says the variable needs to be set

it doesnt say to what.

Jeff Hammond

@jeffhammond

i have never before needed to set it when i set the MPI compilers

-DMPI_CXX_COMPILER=CC -DMPI_C_COMPILER=cc -DMPI_Fortran_COMPILER=ftn

that should do it

does everywhere else

Ryan H. Lewis

@rhl-

try removing the explicit setting of the include path

Jeff Hammond

@jeffhammond

honestly, at this point, i just want CMake to tell me what the error is

yeah that's where i started and it failed

Ryan H. Lewis

@rhl-

this is the piece of CMake that is giving you a problem:

foreach(MPI_PATH ${MPI_C_INCLUDE_PATH})
if(EXISTS "${MPI_PATH}/mpi.h")
set(MPI_HEADER_PATH ${MPI_PATH})
endif()
endforeach()

Jeff Hammond

@jeffhammond

but i set MPI_C_INCLUDE_PATH such that $MPI_C_INCLUDE_PATH/mpi.h was correct

jhammond@edison12:~> ll $CRAY_MPICH_DIR/include/mpi.h
-rwxr-xr-x 1 root root 127K Jun 27 10:30 /opt/cray/mpt/7.4.1/gni/mpich-cray/8.3/include/mpi.h

Ryan H. Lewis

@rhl-

can you just print ${MPI_PATH}/mpi.h and see what it is?

Jeff Hammond

@jeffhammond

i added the appropriate command at line 69 but it had no effect. i'm trying other things now.

Jeff Hammond

@jeffhammond

what's unfortunate is that the mpi.h existence check is to accommodate OpenMPI's bugs.

Ryan H. Lewis

@rhl-

what do you mean?

what was ${MPI_PATH} set to?

Jeff Hammond

@jeffhammond

look at cmake/detect/MPI.cmake

Ryan H. Lewis

@rhl-

I am..

Jeff Hammond

@jeffhammond

message(STATUS "JEFF: ${MPI_C_INCLUDE_PATH}")
message(STATUS "JEFF: ${MPI_PATH}")
message(STATUS "JEFF: ${MPI_HEADER_PATH}")

Chat via Matrix