[Paraview] Paraview server using off-screen rendering
Ganesh Vijayakumar
ganesh.iitm at gmail.com
Thu Jul 16 12:20:36 EDT 2015
Dear Chuck,
The machine is NICS - Darter -
http://www.nics.tennessee.edu/computing-resources/darter. The last I
checked, there's no paraview module on Darter. Hence my attempt at the
installation.
On Thu, Jul 16, 2015 at 11:23 AM Chuck Atkins <chuck.atkins at kitware.com>
wrote:
> Hi Ganesh,
>
> WARNING: Target "vtkParallelMPI" requests linking to directory
>> "/opt/cray/mpt/7.1.3/gni/mpich2-gnu/49/lib/". Targets may link only
>> to libraries. CMake is dropping the item.
>>
>
> 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.
>
This is what I have from ccmake window. Does this seem right?
CMAKE_AR /usr/bin/ar
CMAKE_BUILD_TYPE Release
CMAKE_COLOR_MAKEFILE ON
CMAKE_CXX_COMPILER /opt/cray/craype/2.2.1/bin/CC
CMAKE_CXX_FLAGS
-L/lustre/medusa/gantech/software/mesa-10.6.0/lib
CMAKE_CXX_FLAGS_DEBUG -g
CMAKE_CXX_FLAGS_MINSIZEREL -Os -DNDEBUG
CMAKE_CXX_FLAGS_RELEASE -O3 -DNDEBUG
CMAKE_CXX_FLAGS_RELWITHDEBINFO -O2 -g -DNDEBUG
CMAKE_C_COMPILER /opt/cray/craype/2.2.1/bin/cc
CMAKE_C_FLAGS
-L/lustre/medusa/gantech/software/mesa-10.6.0/lib
CMAKE_C_FLAGS_DEBUG -g
CMAKE_C_FLAGS_MINSIZEREL -Os -DNDEBUG
CMAKE_C_FLAGS_RELEASE -O3 -DNDEBUG
CMAKE_C_FLAGS_RELWITHDEBINFO -O2 -g -DNDEBUG
CMAKE_EXE_LINKER_FLAGS
-L/lustre/medusa/gantech/software/mesa-10.6.0/lib
CMAKE_EXE_LINKER_FLAGS_DEBUG
CMAKE_EXE_LINKER_FLAGS_MINSIZE
CMAKE_EXE_LINKER_FLAGS_RELEASE
CMAKE_EXE_LINKER_FLAGS_RELWITH
CMAKE_EXPORT_COMPILE_COMMANDS OFF
CMAKE_Fortran_COMPILER /opt/gcc/4.9.2/bin/gfortran
CMAKE_Fortran_FLAGS
CMAKE_Fortran_FLAGS_DEBUG -g
CMAKE_Fortran_FLAGS_MINSIZEREL -Os
CMAKE_Fortran_FLAGS_RELEASE -O3
CMAKE_Fortran_FLAGS_RELWITHDEB -O2 -g -DNDEBUG
CMAKE_HP_PTHREADS OFF
CMAKE_INSTALL_PREFIX
/lustre/medusa/gantech/software/Paraview-v4.3.1
CMAKE_LINKER /sw/xc30/xalt/0.5.3-1/sles11.2/bin/ld
CMAKE_MAKE_PROGRAM /usr/bin/gmake
MPIEXEC aprun
MPIEXEC_MAX_NUMPROCS 2
MPIEXEC_NUMPROC_FLAG -n
MPIEXEC_POSTFLAGS
MPIEXEC_PREFLAGS
MPI_CXX_COMPILER /opt/cray/craype/2.2.1/bin/CC
MPI_CXX_COMPILE_FLAGS
MPI_CXX_INCLUDE_PATH
/opt/cray/mpt/7.1.3/gni/mpich2-gnu/49/include
MPI_CXX_LIBRARIES /opt/cray/mpt/7.1.3/gni/mpich2-gnu/49/lib/
MPI_CXX_LINK_FLAGS
MPI_CXX_NO_INTERROGATE /opt/cray/craype/2.2.1/bin/CC
MPI_C_COMPILER /opt/cray/craype/2.2.1/bin/cc
MPI_C_COMPILE_FLAGS
MPI_C_INCLUDE_PATH
/opt/cray/mpt/7.1.3/gni/mpich2-gnu/49/include
MPI_C_LIBRARIES /opt/cray/mpt/7.1.3/gni/mpich2-gnu/49/lib/
MPI_C_LINK_FLAGS
MPI_C_NO_INTERROGATE /opt/cray/craype/2.2.1/bin/cc
MPI_EXTRA_LIBRARY MPI_EXTRA_LIBRARY-NOTFOUND
MPI_Fortran_COMPILER /opt/cray/craype/2.2.1/bin/ftn
MPI_Fortran_COMPILE_FLAGS
MPI_Fortran_INCLUDE_PATH
MPI_Fortran_LIBRARIES
MPI_Fortran_LINK_FLAGS
MPI_LIBRARY /opt/cray/mpt/7.1.3/gni/mpich2-gnu/49/lib
> If it's a problem with HDF5 library, I'm not sure where I need to point to
>> the system installation.
>>
>
> 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.
>
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?
>
> If you're using the bash shell, the following sequence should prep your
> environment accordingly:
>
> # Start with a pristine environment
> module purge
> module load modules
>
> # Load the compilers
> module load PrgEnv-gnu
>
> # Use the Cray wrappers for the compilers instead of calling gcc and g++
> directly
> export CC=$(which cc)
> export CXX=$(which CC)
> export FC=$(which ftn)
>
> # Load the Cray-provided libraries
> module load cray-hdf5
> module load cray-mpich
>
> # Used by the CMake FindHDF5.cmake module
> export HDF5_ROOT=${HDF5_DIR}
>
> Try configuring ParaView starting from that environment.
>
I tried this. I get the same warnings. Any other advice?
>
> Out of curiosity, where is the machine located? We maintain ParaView
> installations at many different HPC sites on a range of Cray systems.
>
> - Chuck Atkins
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150716/38a62d42/attachment.html>
More information about the ParaView
mailing list