<div dir="ltr">Dear Chuck,<br><br><div>  The machine is NICS - Darter - <a href="http://www.nics.tennessee.edu/computing-resources/darter">http://www.nics.tennessee.edu/computing-resources/darter</a>. The last I checked, there's no paraview module on Darter. Hence my attempt at the installation.<br></div><div> <br><div class="gmail_quote"><div dir="ltr">On Thu, Jul 16, 2015 at 11:23 AM Chuck Atkins <<a href="mailto:chuck.atkins@kitware.com">chuck.atkins@kitware.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi Ganesh,<br><br><div class="gmail_extra"><div class="gmail_quote"></div></div></div><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">WARNING: Target "vtkParallelMPI" requests linking to directory "/opt/cray/mpt/7.1.3/gni/mpich2-gnu/49/lib/".  Targets may link only<br><div><div><div class="gmail_quote"><div dir="ltr"><div><div><div> to libraries.  CMake is dropping the item.<br></div></div></div></div></div></div></div></div></blockquote><div><br></div></div></div></div><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div>It looks like you're building with GCC on a Cray.  Are you using gcc directly or are you using the wrappers provides by the PrgEnv-gnu module?  The CMake FindMPI module should work correctly with the Cray wrappers.  In that case, cc and CC will work as mpicc and mpiCC, automatically wrapping the Cray MPI libraries into the compiler args, which the FindMPI module can detect appropriately.<br></div></div></div></div></blockquote><div><br></div><div>This is what I have from ccmake window. Does this seem right?<br><br> CMAKE_AR                         /usr/bin/ar<br> CMAKE_BUILD_TYPE                 Release<br> CMAKE_COLOR_MAKEFILE             ON<br> CMAKE_CXX_COMPILER               /opt/cray/craype/2.2.1/bin/CC<br> CMAKE_CXX_FLAGS                  -L/lustre/medusa/gantech/software/mesa-10.6.0/lib<br> CMAKE_CXX_FLAGS_DEBUG            -g<br> CMAKE_CXX_FLAGS_MINSIZEREL       -Os -DNDEBUG<br> CMAKE_CXX_FLAGS_RELEASE          -O3 -DNDEBUG<br> CMAKE_CXX_FLAGS_RELWITHDEBINFO   -O2 -g -DNDEBUG<br> CMAKE_C_COMPILER                 /opt/cray/craype/2.2.1/bin/cc<br> CMAKE_C_FLAGS                    -L/lustre/medusa/gantech/software/mesa-10.6.0/lib<br> CMAKE_C_FLAGS_DEBUG              -g<br> CMAKE_C_FLAGS_MINSIZEREL         -Os -DNDEBUG<br> CMAKE_C_FLAGS_RELEASE            -O3 -DNDEBUG<br> CMAKE_C_FLAGS_RELWITHDEBINFO     -O2 -g -DNDEBUG<br> CMAKE_EXE_LINKER_FLAGS           -L/lustre/medusa/gantech/software/mesa-10.6.0/lib<br> CMAKE_EXE_LINKER_FLAGS_DEBUG<br> CMAKE_EXE_LINKER_FLAGS_MINSIZE<br> CMAKE_EXE_LINKER_FLAGS_RELEASE<br> CMAKE_EXE_LINKER_FLAGS_RELWITH<br> CMAKE_EXPORT_COMPILE_COMMANDS    OFF<br> CMAKE_Fortran_COMPILER           /opt/gcc/4.9.2/bin/gfortran<br> CMAKE_Fortran_FLAGS<br> CMAKE_Fortran_FLAGS_DEBUG        -g<br> CMAKE_Fortran_FLAGS_MINSIZEREL   -Os<br> CMAKE_Fortran_FLAGS_RELEASE      -O3<br> CMAKE_Fortran_FLAGS_RELWITHDEB   -O2 -g -DNDEBUG<br> CMAKE_HP_PTHREADS                OFF<br> CMAKE_INSTALL_PREFIX             /lustre/medusa/gantech/software/Paraview-v4.3.1<br> CMAKE_LINKER                     /sw/xc30/xalt/0.5.3-1/sles11.2/bin/ld<br> CMAKE_MAKE_PROGRAM               /usr/bin/gmake<br><br> MPIEXEC                          aprun<br> MPIEXEC_MAX_NUMPROCS             2<br> MPIEXEC_NUMPROC_FLAG             -n<br> MPIEXEC_POSTFLAGS<br> MPIEXEC_PREFLAGS<br> MPI_CXX_COMPILER                 /opt/cray/craype/2.2.1/bin/CC<br> MPI_CXX_COMPILE_FLAGS<br> MPI_CXX_INCLUDE_PATH             /opt/cray/mpt/7.1.3/gni/mpich2-gnu/49/include<br> MPI_CXX_LIBRARIES                /opt/cray/mpt/7.1.3/gni/mpich2-gnu/49/lib/<br> MPI_CXX_LINK_FLAGS<br> MPI_CXX_NO_INTERROGATE           /opt/cray/craype/2.2.1/bin/CC<br> MPI_C_COMPILER                   /opt/cray/craype/2.2.1/bin/cc<br> MPI_C_COMPILE_FLAGS<br> MPI_C_INCLUDE_PATH               /opt/cray/mpt/7.1.3/gni/mpich2-gnu/49/include<br> MPI_C_LIBRARIES                  /opt/cray/mpt/7.1.3/gni/mpich2-gnu/49/lib/<br> MPI_C_LINK_FLAGS<br> MPI_C_NO_INTERROGATE             /opt/cray/craype/2.2.1/bin/cc<br> MPI_EXTRA_LIBRARY                MPI_EXTRA_LIBRARY-NOTFOUND<br> MPI_Fortran_COMPILER             /opt/cray/craype/2.2.1/bin/ftn<br> MPI_Fortran_COMPILE_FLAGS<br> MPI_Fortran_INCLUDE_PATH<br> MPI_Fortran_LIBRARIES<br> MPI_Fortran_LINK_FLAGS<br> MPI_LIBRARY                      /opt/cray/mpt/7.1.3/gni/mpich2-gnu/49/lib<br><br> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div></div></div></div></div><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div><div class="gmail_quote"><div dir="ltr"><div><div></div>If it's a problem with HDF5 library, I'm not sure where I need to point to the system installation.<br></div></div></div></div></div></div></blockquote></div></div></div><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"></div><br></div><div class="gmail_extra">If you load the cray-hdf5 module, that will set the HDF5_DIR environment variable to the correct location.  Unfortunately, CMake uses the HDF5_ROOT variable instead to look for it so you'll neet to set it accordingly.<br></div></div></blockquote><div><br></div><div>I don't have much experience with cmake, but can I set additional variables in the ccmake window? Should this variable show up there asking to be set if you turn on the advanced mode toggle?<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><br>If you're using the bash shell, the following sequence should prep your environment accordingly:<br><span style="font-family:monospace,monospace"><br># Start with a pristine environment<br>module purge<br></span></div><div class="gmail_extra"><span style="font-family:monospace,monospace">module load modules<br></span></div><div class="gmail_extra"><span style="font-family:monospace,monospace"><br># Load the compilers<br>module load PrgEnv-gnu<br><br># Use the Cray wrappers for the compilers instead of calling gcc and g++ directly<br>export CC=$(which cc)<br>export CXX=$(which CC)<br>export FC=$(which ftn)<br><br># Load the Cray-provided libraries<br>module load cray-hdf5<br>module load cray-mpich<br><br># Used by the CMake FindHDF5.cmake module<br>export HDF5_ROOT=${HDF5_DIR}</span><br><br></div><div class="gmail_extra">Try configuring ParaView starting from that environment.<br></div></div></blockquote><div><br></div><div>I tried this. I get the same warnings. Any other advice?<br> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><br></div><div class="gmail_extra">Out of curiosity, where is the machine located?  We maintain ParaView installations at many different HPC sites on a range of Cray systems.<br><br></div></div><div dir="ltr"><div class="gmail_extra">- Chuck Atkins<br></div></div></blockquote></div></div></div>