[vtkusers] Building VTK on a BlueGene/P

François Bissey fbissey at slingshot.co.nz
Thu Sep 12 19:32:57 EDT 2013


On 2013-09-11 14:19, David E DeMarle wrote:
> Refer to:
> http://paraview.org/Wiki/ParaView/Users_Guide/Parallel_Rendering [1]
> And try:
> 
> 		VTK_USE_COCOA
> 		OFF
> 		Mac only.
> 
> 		VTK_USE_X
> 		OFF
> 
> 		VTK_USE_OFFSCREEN
> 		ON
> 
> 		VTK_OPENGL_HAS_OSMESA
> 		ON
> 		 Turn this to ON to enable Off Screen MESA.
> 
> 		OSMESA_INCLUDE_DIR
> 		<mesa include dir>
> 		Set this to the include directory for MESA.
> 
> 		OPENGL_INCLUDE_DIR
> 		<mesa include dir>
> 		Set this to the include directory for MESA.
> 
> 		OPENGL_gl_LIBRARY
> 		<empty>
> 		Set this to empty.
> 
> 		OPENGL_glu_LIBRARY
> 		libGLU
> 		Set this to the libGLU.a or libGLU.so file.
> 
> 		OSMESA_LIBRARY
> 		 libOSMesa
> 		Set this to the libOSMesa.a or libOSMesa.so file.
> 
Thanks that was very useful, especially since I didn't know that libGLU 
was a dependency.
The only difference with that page is OSMESA_INCLUDE_DIR seem to have 
been replaced with OPENGL_xmesa_INCLUDE_DIR. Also bluegeneL tryrun file 
is definitely not current. cmake asked me for more info. It is also a 
bit unclear how to treat the *__TRYRUN_OUTPUT variables.

I now hit difficulties with HDF5.

[ 61%] Building C object 
ThirdParty/hdf5/vtkhdf5/src/CMakeFiles/vtkhdf5.dir/H5F.c.o
cd /bgp/local/pkg/downloads/build_vtk6.0_bgp/ThirdParty/hdf5/vtkhdf5/src 
&& 
/bgsys/drivers/V1R4M2_200_2010-100508P/ppc/gcc-4.3.2/gnu-linux/bin/powerpc-bgp-linux-gcc  -DDEBUG -DH5AC_DEBUG -DH5B_DEBUG -DH5D_DEBUG -DH5E_DEBUG -DH5F_DEBUG -DH5G_DEBUG -DH5HG_DEBUG -DH5HL_DEBUG -DH5I_DEBUG -DH5MF_DEBUG -DH5MM_DEBUG -DH5O_DEBUG -DH5P_DEBUG -DH5S_DEBUG -DH5T_DEBUG -DH5V_DEBUG -DH5Z_DEBUG -DH5_DEBUG_API -DVTK_IN_VTK -Dhdf5_EXPORTS -w -w -std=c99 -fomit-frame-pointer -finline-functions -fno-common -w -fmessage-length=0 -g -fPIC -I/bgp/local/pkg/downloads/build_vtk6.0_bgp/ThirdParty/zlib -I/bgp/local/pkg/downloads/VTK6.0.0/ThirdParty/zlib -I/bgp/local/pkg/downloads/build_vtk6.0_bgp/ThirdParty/hdf5/vtkhdf5 -I/bgp/local/pkg/downloads/VTK6.0.0/ThirdParty/hdf5/vtkhdf5/hl/src -I/bgp/local/pkg/downloads/VTK6.0.0/ThirdParty/hdf5/vtkhdf5/src -I/bgp/local/pkg/downloads/build_vtk6.0_bgp/ThirdParty/hdf5 -I/bgp/local/pkg/downloads/VTK6.0.0/ThirdParty/hdf5 -I/bgp/local/pkg/downloads/VTK6.0.0/ThirdParty/hdf5/vtkhdf5 -I/bgp/local/pkg/downloads/build_vtk6.0_bgp    -UNDEBUG -o
CMakeFiles/vtkhdf5.dir/H5F.c.o   -c /bgp/local/pkg/downloads/VTK6.0.0/ThirdParty/hdf5/vtkhdf5/src/H5F.c
/bgp/local/pkg/downloads/VTK6.0.0/ThirdParty/hdf5/vtkhdf5/src/H5F.c: In 
function ‘H5F_build_actual_name’:
/bgp/local/pkg/downloads/VTK6.0.0/ThirdParty/hdf5/vtkhdf5/src/H5F.c:2223: error: ‘S_IFLNK’ undeclared (first use in this function)
/bgp/local/pkg/downloads/VTK6.0.0/ThirdParty/hdf5/vtkhdf5/src/H5F.c:2223: error: (Each undeclared identifier is reported only once
/bgp/local/pkg/downloads/VTK6.0.0/ThirdParty/hdf5/vtkhdf5/src/H5F.c:2223: error: for each function it appears in.)
/bgp/local/pkg/downloads/VTK6.0.0/ThirdParty/hdf5/vtkhdf5/src/H5F.c:2223: error: ‘S_IFMT’ undeclared (first use in this function)
/bgp/local/pkg/downloads/VTK6.0.0/ThirdParty/hdf5/vtkhdf5/src/H5F.c:2228: error: ‘PATH_MAX’ undeclared (first use in this function)
make[2]: *** 
[ThirdParty/hdf5/vtkhdf5/src/CMakeFiles/vtkhdf5.dir/H5F.c.o] Error 1


Googling I found out the following vtk bug in mantis:
http://vtk.org/Bug/view.php?id=12568

After poking around my build tree I found that CMAKE_SYSTEM is set to 
"BlueGeneP-dynamic" rather
than plain Linux. If I set CMAKE_SYSTEM=Linux and 
CMAKE_SYSTEM_NAME=BlueGeneP-* it all gets back to being defined as a 
Linux system rather than a BlueGene. So I will edit the relevant hdf5 
file to extent to BlueGene.

I also tried using an external hdf5. And it was a bit surreal not unlike 
my experiences with paraview 3.98 a while ago 
(http://www.paraview.org/pipermail/paraview/2012-November/026601.html) 
this time camke complained HDF5_LIBRARIES was not found but I am only 
offered HDF5_hdf5_LIBRARY in ccmake.
It looks like there may be confusion in HDF5 variable names in various 
cmake files.

Francois



More information about the vtkusers mailing list