[Paraview] Oggtheora message while configuring ParaView

[David E DeMarle]

Hey Bill,

I've built ParaView on Crays (including Titan).

The approach I recommend is cross compilation. See the Mastering CMake book
chapter 8 for the details. The approach works for Crays and BlueGenes at
least as far back as XT3 and BG/L.

It boils down to building twice, once on and for the login nodes, and then
again on the login nodes but for the compute nodes.
The first pass just builds the tools that make uses when you compile
Paraview (like the protoc compiler). The second pass uses those tools and a
file with the necessary TryRunResults containing answers to the things that
the front end build can not determine
(like HDF5_PRINTF_LL_TEST_RUN__TRYRUN_OUTPUT) to build a ParaView that will
run on the compute nodes.

Yes it can be just as much fun as that sounds!

Lucky for you we've packaged up the whole thing in ParaViewSuperbuild
(git://paraview.org/ParaViewSuperbuild.git). Superbuild does all of the
above and builds ParaView's dependencies at the same time (osmesa, python).

To use it on Titan for instance, first source something like this in a
"tools" directory to setup the tools build pass

titan/v4.0.1> cat configtools.sh
#use my own cmake, system one is too old
setenv PATH
/autofs/na4_proj/csc035/demarle/pvdev/titan/cmake-build/bin:${PATH}
#switch compiler to compile code for front end
module unload PrgEnv-pgi
module load gcc
#configure settings for to build compile tools only
cmake \
  -DCROSS_BUILD_STAGE:STRING=TOOLS -Dcross_target:STRING=xk7_gnu \
  -DCMAKE_BUILD_TYPE:STRING=Release \
  -DBUILD_TESTING:BOOL=FALSE \
  -DParaView_FROM_GIT:BOOL=OFF \
  -DENABLE_paraview:BOOL=TRUE \
  -DENABLE_boost:BOOL=TRUE \
  -DENABLE_python:BOOL=TRUE \
  -DENABLE_portfwd:BOOL=FALSE \
  ../../ParaviewSuperbuild

than type make.

Next source something like this to setup the cross build pass in a "cross"
directory.

titan/v4.0.1> cat configcross.sh
#use my own cmake, system one is too old
setenv PATH
/autofs/na4_proj/csc035/demarle/pvdev/titan/cmake-build/bin:${PATH}
#switch compiler to compile code for back end
module unload PrgEnv-pgi
module unload gcc
module load PrgEnv-gnu
#not sure why module load wasn't sufficient, but ended up needing to force
#cmake to choose the right compiler
setenv CC /opt/cray/xt-asyncpe/5.17/bin/cc
setenv CXX /opt/cray/xt-asyncpe/5.17/bin/CC
#configure settings to cross compile python, (mesa - implied), and paraview
cmake \
  -DCROSS_BUILD_STAGE:STRING=CROSS -Dcross_target:STRING=xk7_gnu \
  -DCMAKE_BUILD_TYPE:STRING=Release \
  -DBUILD_TESTING:BOOL=TRUE \
  -DParaView_FROM_GIT:BOOL=OFF \
  -DENABLE_paraview:BOOL=TRUE \
  -DENABLE_python:BOOL=TRUE \
  ../../ParaviewSuperbuild

than type make.

The cross built binary will end up in paraview/src/paraview-bld. You will
need to put the binaries and the python libs and paraview python modules
somewhere on the parallel file system in order to run it. I recommend
against building directly on the parallel file system as that slows down
the build immensely.

cheers

David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909


On Wed, Aug 14, 2013 at 11:04 AM, Bill Sherman <shermanw at indiana.edu> wrote:

> Utkarsh,
>
>
>  Looks like CHECK_TYPE_SIZE(..) calls made by cmake to discover various
>> type sizes just fails (not just for OggTheora but also for HDF5 and
>> IceT).  To confirm that, try running cmake on the attached
>> CMakeLists.txt as
>>
>
> Okay, done.
>
> I should probably mention (if I haven't already) that this is being done
> under the Cray version of SUSE enterprise Linux for a Cray XE/XK7 system
> (along the lines of Blue Waters and Titan).
>
> And I tested it twice, once with the Cray compiler, and then again with
> the GNU compiler.  Both times I got the exact same result as you report
> here:
>
>
>  What does it print out (ensure correct compiler is being used)? For me
>> it prints the following message:
>>
>> HAVE_VTKOGGTHEORA_INT16_T=TRUE
>>       VTKOGGTHEORA_INT16_T=2
>>
>> HAVE_VTKOGGTHEORA_INT=TRUE
>>       VTKOGGTHEORA_INT=4
>>
>
> Are you aware of anyone at NCSA or Oak Ridge that have had success
> on their Cray systems?
>
> What should I try next?
>
>         Thanks,
>         Bill
>
>
> ______________________________**_________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/**
> opensource/opensource.html<http://www.kitware.com/opensource/opensource.html>
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/**ParaView <http://paraview.org/Wiki/ParaView>
>
> Follow this link to subscribe/unsubscribe:
> http://www.paraview.org/**mailman/listinfo/paraview<http://www.paraview.org/mailman/listinfo/paraview>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.paraview.org/pipermail/paraview/attachments/20130814/10d8636e/attachment-0001.htm>