[Paraview] Paraview server using off-screen rendering

[Ganesh Vijayakumar]

Hello,

  I'm trying to install paraview-4.3.1 on a cluster with off-screen
rendering. I'm following instructions on the wiki. I installed mesa-10.6.0
and included that


I get a whole bunch of warnings after i do ccmake like these.

 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.

Probably about 50 or so of these with various vtk classes saying the same
thing. I'm trying to use the system's cray-mpich2 library. Hence I use the
MPI_CXX_NO_INTERROGATE and  MPI_C_NO_INTERROGATE variables. However, I
realize that MPI_LIBRARY currently points to a directory. I'm not sure if
this is even relevant. If it is, I don't know how to get rid of it. I tried
replacing this variable with a semicolon separated list of individual files
inside the MPI library to link it to. But on performing configure it gives
the same set of warnings and worse.. it reverts back to the original
setting of pointing to a directory.

If I ignore these and continue ahead with the make, this is what I get.

Scanning dependencies of target H5detect
[  3%] Building C object
VTK/ThirdParty/hdf5/vtkhdf5/src/CMakeFiles/H5detect.dir/H5detect.c.o
Linking CXX shared library ../../../../lib/libvtkjsoncpp-pv4.3.so
[  3%] Built target vtkjsoncpp
Linking C executable ../../../../../bin/H5detect
Scanning dependencies of target H5make_libsettings
[  4%] Building C object
VTK/ThirdParty/hdf5/vtkhdf5/src/CMakeFiles/H5make_libsettings.dir/H5make_libsettings.c.o
Linking C executable ../../../../../bin/H5make_libsettings
/usr/lib/../lib64/libpthread.a(lowlevellock.o): In function
`__lll_lock_wait_private':
/usr/src/packages/BUILD/glibc-2.11.3/nptl/../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:81:
multiple definition of `__lll_lock
_wait_private'
/usr/lib/../lib64/libc.a(libc-lowlevellock.o):/usr/src/packages/BUILD/glibc-2.11.3/nptl/../nptl/sysdeps/unix/sysv/linux/x86_64/lowleve
llock.S:81: first defined here
/usr/lib/../lib64/libpthread.a(lowlevellock.o): In function
`__lll_unlock_wake_private':
/usr/src/packages/BUILD/glibc-2.11.3/nptl/../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:323:
multiple definition of `__lll_unl
ock_wake_private'
/usr/lib/../lib64/libc.a(libc-lowlevellock.o):/usr/src/packages/BUILD/glibc-2.11.3/nptl/../nptl/sysdeps/unix/sysv/linux/x86_64/lowleve
llock.S:323: first defined here
/usr/bin/ld: link errors found, deleting executable
`../../../bin/vtkWrapPythonInit-pv4.3'
collect2: error: ld returned 1 exit status
make[2]: *** [bin/vtkWrapPythonInit-pv4.3] Error 1
make[1]: *** [VTK/Wrapping/Tools/CMakeFiles/vtkWrapPythonInit.dir/all]
Error 2
make[1]: *** Waiting for unfinished jobs....
[  4%] Building C object
VTK/ThirdParty/zlib/vtkzlib/CMakeFiles/vtkzlib.dir/zutil.c.o
Linking C shared library ../../../../lib/libvtkzlib-pv4.3.so
/usr/lib/../lib64/libpthread.a(lowlevellock.o): In function
`__lll_lock_wait_private':
/usr/src/packages/BUILD/glibc-2.11.3/nptl/../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:81:
multiple definition of `__lll_lock
_wait_private'
/usr/lib/../lib64/libc.a(libc-lowlevellock.o):/usr/src/packages/BUILD/glibc-2.11.3/nptl/../nptl/sysdeps/unix/sysv/linux/x86_64/lowleve
llock.S:81: first defined here
/usr/lib/../lib64/libpthread.a(lowlevellock.o): In function
`__lll_unlock_wake_private':
/usr/src/packages/BUILD/glibc-2.11.3/nptl/../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:323:
multiple definition of `__lll_unl
ock_wake_private'

There's more. But I'm not sure. what exactly the error is. If it's a
problem with HDF5 library, I'm not sure where I need to point to the system
installation. Should I point to a parallel-HDF5 or a serial HDF5? I do need
HDF5 support through XDMF... I guess parallel is better. But I could take
care of that at a later date. I need something (without HDF5 even) working
now.

ganesh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20150716/4a5019a8/attachment.html>