<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Thu, Aug 29, 2013 at 2:13 PM, Hong Yi <span dir="ltr"><<a href="mailto:hongyi@renci.org" target="_blank">hongyi@renci.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<div style="direction:ltr;font-size:10pt;font-family:Tahoma">Hi David,<br>
<br>
I just started to try superbuild on Titan also. I don't see you set ENABLE_MPI to be true in your configure script. Could you confirm whether ENABLE_MPI needs to be set to TRUE in order for ParaView to run on Titan in parallel? Since my purpose is to link our</div>
</div></blockquote><div><br></div><div style>The ENABLE_MPI flag at the Superbuild level is unrelated. It has a purpose only when CROSS_BUILD_STAGE=HOST, that is when making ParaView binary installers for desktops from Superbuild. </div>
<div style><br></div><div style>You shouldn't turn it on in the TOOLS or CROSS stages. Instead let the CROSS stage use the system installed MPI. It does that by turning PARAVIEW_USE_MPI=ON when it configures the ParaView sub-build. See CMake/crosscompile/xk7_gnu to see where it does that, and to see the other flags it uses.</div>
<div style> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div style="direction:ltr;font-size:10pt;font-family:Tahoma">
simulation code (already built statically with CMake on Titan) to ParaView CoProcessing libraries (I am using version 3.98.1) for in-situ visualization on Titan, so in this case, do I have to set ENABLE_paraview to true and do I need to enable OSMesa for ParaView
to resort to off-screen rendering for in-situ visualization? <br></div></div></blockquote><div><br></div><div style>The CROSS stage turns on Python, Mesa and ParaView. Titan's accelerators don't really run X11, so Mesa is the only option for rendering there.</div>
<div style><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div style="direction:ltr;font-size:10pt;font-family:Tahoma">
Although I can build ParaView from source on Titan login nodes, I am not able to run it on compute nodes, so I am starting to try superbuild hoping to be able to cross build ParaView libraries to run in-situ visualization on Titan.<br>
</div></div></blockquote><div><br></div><div style>I've cross compiled Catalyst itself before on a bluegene. I did it manually before SuperBuild existed. I will see if I can dig up my config scripts. Cross compiling Catalyst should be more or less that same thing as cross compiling ParaView, but a bit faster and easier because their is less code involved.</div>
<div style><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div style="direction:ltr;font-size:10pt;font-family:Tahoma">
Thanks,<br>
Hong<br>
<br>
<div style="font-size:16px;font-family:Times New Roman">
<hr>
<div style="direction:ltr"><font color="#000000" face="Tahoma"><b>From:</b> <a href="mailto:paraview-bounces@paraview.org" target="_blank">paraview-bounces@paraview.org</a> [<a href="mailto:paraview-bounces@paraview.org" target="_blank">paraview-bounces@paraview.org</a>] on behalf of David E DeMarle [<a href="mailto:dave.demarle@kitware.com" target="_blank">dave.demarle@kitware.com</a>]<br>
<b>Sent:</b> Thursday, August 29, 2013 1:21 PM<div class="im"><br>
<b>To:</b> Vanmoer, Mark W<br>
<b>Cc:</b> <a href="mailto:paraview@paraview.org" target="_blank">paraview@paraview.org</a><br>
<b>Subject:</b> Re: [Paraview] Building on Titan using ParaViewSuperbuild<br>
</div></font><br>
</div><div><div class="h5">
<div></div>
<div>
<div dir="ltr">Your tools build is pointing to the compiler wrapper that you normally would use to make code for the back end.
<div>The tools build should just use plain old local gcc since we only build things at that point that run on the login node.</div>
<div><br>
</div>
<div>Try these setup scripts:</div>
<div>I source configtools.sh to set up my environment before I build the compile tools, and configcross.sh before before I cross compile ParaView.</div>
<div><br>
</div>
<div>configtools.sh</div>
<div>
<div>#use my own cmake, system one is too old</div>
<div>setenv PATH /autofs/na4_proj/csc035/demarle/pvdev/titan/cmake-build/bin:${PATH}</div>
<div>#switch compiler to compile code for front end</div>
<div>module unload PrgEnv-pgi</div>
<div>module load gcc</div>
<div>#configure settings for to build compile tools only</div>
<div>cmake \</div>
<div> -DCROSS_BUILD_STAGE:STRING=TOOLS -Dcross_target:STRING=xk7_gnu \</div>
<div> -DCMAKE_BUILD_TYPE:STRING=Release \</div>
<div> -DBUILD_TESTING:BOOL=FALSE \</div>
<div> -DParaView_FROM_GIT:BOOL=OFF \</div>
<div> -DENABLE_paraview:BOOL=TRUE \</div>
<div> -DENABLE_boost:BOOL=TRUE \</div>
<div> -DENABLE_python:BOOL=TRUE \</div>
<div> -DENABLE_portfwd:BOOL=FALSE \</div>
<div> ../../ParaViewSuperbuild</div>
<div><br>
</div>
<div><br>
</div>
<div>then make</div>
<div><br>
</div>
<div>configcross.sh</div>
<div>
<div>#use my own cmake, system one is too old</div>
<div>setenv PATH /autofs/na4_proj/csc035/demarle/pvdev/titan/cmake-build/bin:${PATH}</div>
<div>#switch compiler to compile code for back end</div>
<div>module unload PrgEnv-pgi</div>
<div>module unload gcc</div>
<div>module load PrgEnv-gnu</div>
<div>#not sure why module load wasn't sufficient, but ended up needing to force</div>
<div>#cmake to choose the right compiler</div>
<div>setenv CC /opt/cray/xt-asyncpe/5.17/bin/cc</div>
<div>setenv CXX /opt/cray/xt-asyncpe/5.17/bin/CC</div>
<div>#configure settings to cross compile python, (mesa - implied), and paraview</div>
<div>cmake \</div>
<div> -DCROSS_BUILD_STAGE:STRING=CROSS -Dcross_target:STRING=xk7_gnu \</div>
<div> -DCMAKE_BUILD_TYPE:STRING=Release \</div>
<div> -DBUILD_TESTING:BOOL=TRUE \</div>
<div> -DParaView_FROM_GIT:BOOL=OFF \</div>
<div> -DENABLE_paraview:BOOL=TRUE \</div>
<div> -DENABLE_python:BOOL=TRUE \</div>
</div>
<div>
<div> ../../ParaViewSuperbuild</div>
</div>
</div>
<div><br>
</div>
<div>then make again</div>
<div><br>
</div>
</div>
<div class="gmail_extra"><br clear="all">
<div>David E DeMarle<br>
Kitware, Inc.<br>
R&D Engineer<br>
21 Corporate Drive<br>
Clifton Park, NY 12065-8662<br>
Phone: <a href="tel:518-881-4909" value="+15188814909" target="_blank">518-881-4909</a></div>
<br>
<br>
<div class="gmail_quote">On Tue, Aug 27, 2013 at 4:26 PM, Vanmoer, Mark W <span dir="ltr">
<<a href="mailto:mvanmoer@illinois.edu" target="_blank">mvanmoer@illinois.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-US">
<div>
<p class="MsoNormal">Hi, I'm trying to follow the advice on building ParaView on Titan using the ParaViewSuperbuild method from an earlier discussion in June.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">When I run make in the "TOOLS" directory I get the following error:<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">[ 66%] Building CXX object Utilities/ProcessXML/CMakeFiles/kwProcessXML.dir/ProcessXML.cxx.o<u></u><u></u></p>
<p class="MsoNormal">Linking CXX executable ../../bin/vtkkwProcessXML-pv4.0<u></u><u></u></p>
<p class="MsoNormal">/usr/bin/ld: attempted static link of dynamic object `../../lib/libvtkCommonCore-pv4.0.so.1'<u></u><u></u></p>
<p class="MsoNormal">collect2: error: ld returned 1 exit status<u></u><u></u></p>
<p class="MsoNormal">make[6]: *** [bin/vtkkwProcessXML-pv4.0] Error 1<u></u><u></u></p>
<p class="MsoNormal">make[5]: *** [Utilities/ProcessXML/CMakeFiles/kwProcessXML.dir/all] Error 2<u></u><u></u></p>
<p class="MsoNormal">make[4]: *** [CMakeFiles/pvCompileTools.dir/rule] Error 2<u></u><u></u></p>
<p class="MsoNormal">make[3]: *** [pvCompileTools] Error 2<u></u><u></u></p>
<p class="MsoNormal">CMake Error at /ccs/home/vanmoer/builds/superbuild/tools-build/pv-paraview-build.cmake:26 (message):<u></u><u></u></p>
<p class="MsoNormal"> Failed!!!<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">make[2]: *** [paraview/src/paraview-stamp/paraview-build] Error 1<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">I don't see a BUILD_SHARED that I can toggle. All of the CMAKE_SHARED_LINKER_FLAGS* vars are empty, if those are related.
<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Any suggestions?<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Thanks,<u></u><u></u></p>
<p class="MsoNormal">Mark<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
<br>
_______________________________________________<br>
Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">
http://www.kitware.com/opensource/opensource.html</a><br>
<br>
Please keep messages on-topic and check the ParaView Wiki at: <a href="http://paraview.org/Wiki/ParaView" target="_blank">
http://paraview.org/Wiki/ParaView</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://www.paraview.org/mailman/listinfo/paraview" target="_blank">http://www.paraview.org/mailman/listinfo/paraview</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</div>
</div></div></div>
</div>
</div>
</blockquote></div><br></div></div>