<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Thanks for the info, Mark. Looks like it is sensible for me to try newer version of CMake 2.8.11.2 and see how it goes.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">On a somewhat related question: I am trying to pass in some CMake flags to make it build my new filter plugin as well as FortranAdaptor for coprocessing (yes,
I discovered also that coprocessing/catalyst is built by default by superbuild, but FortranAdaptor is turned off by default). I tried to pass it in by adding corresponding –D to configuretools, but got CMake warning as well indicating those manually-specified
variables were not used. I am wondering whether I can do it by directly changing CMakeCache.txt under paraview/src/paraview-build to force the corresponding flags to be on…<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Hong<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Vanmoer, Mark W [mailto:mvanmoer@illinois.edu]
<br>
<b>Sent:</b> Friday, August 30, 2013 5:34 PM<br>
<b>To:</b> Hong Yi; David E DeMarle<br>
<b>Cc:</b> paraview@paraview.org<br>
<b>Subject:</b> RE: [Paraview] Building on Titan using ParaViewSuperbuild<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Hi Hong,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I was able to get David’s instructions to work using CMake 2.8.11.2 and ParaView 4.0.1. The build process seems to be sensitive to versions.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Mark
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Hong Yi [<a href="mailto:hongyi@renci.org">mailto:hongyi@renci.org</a>]
<br>
<b>Sent:</b> Friday, August 30, 2013 3:52 PM<br>
<b>To:</b> David E DeMarle; Vanmoer, Mark W<br>
<b>Cc:</b> <a href="mailto:paraview@paraview.org">paraview@paraview.org</a><br>
<b>Subject:</b> RE: [Paraview] Building on Titan using ParaViewSuperbuild<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">I tried to follow the instructions and the configuration scripts to build ParaView for compute nodes on Titan. It built successfully
without issues for the TOOLS stage, but when doing final linking for paraview in the CROSS stage, I got numerous similar linking error from different lines such as the following:<br>
<br>
----------------<br>
/....../ParaView/ParaViewSuperbuild/cross/paraview/src/paraview/Utilities/mpi4py/src/mpi4py.MPI.c: In function '__pyx_pf_6mpi4py_3MPI_4File_54Sync':<br>
/....../ParaView/ParaViewSuperbuild/cross/paraview/src/paraview/Utilities/mpi4py/src/mpi4py.MPI.c:89682:7: error: '_save' undeclared (first use in this function)<br>
----------------<br>
<br>
The same error message were raised from the same file mpi4py.MPI.c from different lines.<br>
<br>
I am using CMake version 2.8.10.2 which is provided by Titan, and using the ParaView source tree version 3.98 with one additional filter I have developed.<br>
<br>
Any idea on what could cause the linking error?<br>
<br>
Thanks,<br>
Hong <o:p></o:p></span></p>
<div>
<div class="MsoNormal" align="center" style="text-align:center"><span style="color:black">
<hr size="2" width="100%" align="center">
</span></div>
<div id="divRpF565344">
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"> David E DeMarle [dave.demarle@kitware.com]<br>
<b>Sent:</b> Thursday, August 29, 2013 4:08 PM<br>
<b>To:</b> Vanmoer, Mark W<br>
<b>Cc:</b> Hong Yi; <a href="mailto:paraview@paraview.org">paraview@paraview.org</a><br>
<b>Subject:</b> Re: [Paraview] Building on Titan using ParaViewSuperbuild</span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="color:black">On Thu, Aug 29, 2013 at 3:51 PM, Vanmoer, Mark W <<a href="mailto:mvanmoer@illinois.edu" target="_blank">mvanmoer@illinois.edu</a>> wrote:<o:p></o:p></span></p>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">So coprocessing will not be built using the below instructions? I would have mentioned that, but coprocessing appears to</span><span style="color:black"><o:p></o:p></span></p>
</div>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">still be part of a regular, non-cross-compile build, so I figured it was part of ENABLE_paraview </span><span style="color:black"><o:p></o:p></span></p>
</div>
</blockquote>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">The coprocessing plugin, which adds things to the GUI to make it easy to record coprocessing pipeline setups doesn't need to be turned on since that lives in the client only. (It is like python trace or state recording,
but tailored to recording in-situ setups).<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">Catalyst (the stripped down version of ParaView server that a simulation code can link to and use to run those recorded pipelines quickly) is not yet an option in ParaViewSuperbuild. To cross compile Catalyst a
bit more work will be required. It will follow the same plan as how the ParaView server is compiled, but I just haven't tried it. When I did cross compile Catalyst last year at this time I did the same steps that ParaViewSuperbuild's TOOLS and CROSS build
passes did, just by hand.<o:p></o:p></span></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Also, for the below configcross.sh, do we need to pass in a CMake variable telling it where the tools build dir is located?</span><span style="color:black"><o:p></o:p></span></p>
</div>
</div>
</blockquote>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">That should be an option that you can easily set, but it isn't sorry.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> CMake/CrossCompilationMacros.cmake assumes it can find it one directory up and over like so:<o:p></o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="color:black">macro(find_hosttools)<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> set(PARAVIEW_HOSTTOOLS_DIR ${CMAKE_BINARY_DIR}/../tools/paraview/src/paraview-build/ CACHE PATH<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> "Location of host built paraview compile tools directory")<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> set(PYTHON_HOST_EXE ${CMAKE_BINARY_DIR}/../tools/install/bin/python CACHE PATH<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> "Location of host built python executable")<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> set(PYTHON_HOST_LIBDIR ${CMAKE_BINARY_DIR}/../tools/install/lib CACHE PATH<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> "Location of host built python libraries")<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> set(BOOST_HOST_INCLUDEDIR ${CMAKE_BINARY_DIR}/../tools/install/include CACHE PATH<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> "Location of host built boost headers")<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">endmacro()<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">You could predefine all four of those if you like.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
</div>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Thanks,</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Mark</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span style="color:black"><o:p></o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"> David E DeMarle [mailto:<a href="mailto:dave.demarle@kitware.com" target="_blank">dave.demarle@kitware.com</a>]
<br>
<b>Sent:</b> Thursday, August 29, 2013 1:41 PM<br>
<b>To:</b> Hong Yi<br>
<b>Cc:</b> Vanmoer, Mark W; <a href="mailto:paraview@paraview.org" target="_blank">
paraview@paraview.org</a></span><span style="color:black"><o:p></o:p></span></p>
<div>
<div>
<p class="MsoNormal"><span style="color:black"><br>
<b>Subject:</b> Re: [Paraview] Building on Titan using ParaViewSuperbuild<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<div>
<div>
<div>
<p class="MsoNormal"><span style="color:black">On Thu, Aug 29, 2013 at 2:13 PM, Hong Yi <<a href="mailto:hongyi@renci.org" target="_blank">hongyi@renci.org</a>> wrote:<o:p></o:p></span></p>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">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</span><span style="color:black"><o:p></o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">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. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">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.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">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?
</span><span style="color:black"><o:p></o:p></span></p>
</div>
</div>
</blockquote>
<div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">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.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">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.</span><span style="color:black"><o:p></o:p></span></p>
</div>
</div>
</blockquote>
<div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">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.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">Thanks,<br>
Hong</span><span style="color:black"><o:p></o:p></span></p>
<div>
<div class="MsoNormal" align="center" style="text-align:center"><span style="color:black">
<hr size="2" width="100%" align="center">
</span></div>
<div>
<p class="MsoNormal"><b><span style="font-family:"Tahoma","sans-serif";color:black">From:</span></b><span style="font-family:"Tahoma","sans-serif";color:black">
<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</span><span style="color:black"><o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-family:"Tahoma","sans-serif";color:black"><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</span><span style="color:black"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
</div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="color:black">Your tools build is pointing to the compiler wrapper that you normally would use to make code for the back end.
<o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="color:black">The tools build should just use plain old local gcc since we only build things at that point that run on the login node.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">Try these setup scripts:<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">I source configtools.sh to set up my environment before I build the compile tools, and configcross.sh before before I cross compile ParaView.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">configtools.sh<o:p></o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="color:black">#use my own cmake, system one is too old<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">setenv PATH /autofs/na4_proj/csc035/demarle/pvdev/titan/cmake-build/bin:${PATH}<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">#switch compiler to compile code for front end<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">module unload PrgEnv-pgi<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">module load gcc<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">#configure settings for to build compile tools only<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">cmake \<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> -DCROSS_BUILD_STAGE:STRING=TOOLS -Dcross_target:STRING=xk7_gnu \<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> -DCMAKE_BUILD_TYPE:STRING=Release \<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> -DBUILD_TESTING:BOOL=FALSE \<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> -DParaView_FROM_GIT:BOOL=OFF \<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> -DENABLE_paraview:BOOL=TRUE \<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> -DENABLE_boost:BOOL=TRUE \<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> -DENABLE_python:BOOL=TRUE \<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> -DENABLE_portfwd:BOOL=FALSE \<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> ../../ParaViewSuperbuild<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">then make<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">configcross.sh<o:p></o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="color:black">#use my own cmake, system one is too old<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">setenv PATH /autofs/na4_proj/csc035/demarle/pvdev/titan/cmake-build/bin:${PATH}<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">#switch compiler to compile code for back end<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">module unload PrgEnv-pgi<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">module unload gcc<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">module load PrgEnv-gnu<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">#not sure why module load wasn't sufficient, but ended up needing to force<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">#cmake to choose the right compiler<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">setenv CC /opt/cray/xt-asyncpe/5.17/bin/cc<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">setenv CXX /opt/cray/xt-asyncpe/5.17/bin/CC<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">#configure settings to cross compile python, (mesa - implied), and paraview<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">cmake \<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> -DCROSS_BUILD_STAGE:STRING=CROSS -Dcross_target:STRING=xk7_gnu \<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> -DCMAKE_BUILD_TYPE:STRING=Release \<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> -DBUILD_TESTING:BOOL=TRUE \<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> -DParaView_FROM_GIT:BOOL=OFF \<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> -DENABLE_paraview:BOOL=TRUE \<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> -DENABLE_python:BOOL=TRUE \<o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="color:black"> ../../ParaViewSuperbuild<o:p></o:p></span></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">then make again<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><br clear="all">
<o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="color:black">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" target="_blank">518-881-4909</a><o:p></o:p></span></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="color:black"> <o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="color:black">On Tue, Aug 27, 2013 at 4:26 PM, Vanmoer, Mark W <<a href="mailto:mvanmoer@illinois.edu" target="_blank">mvanmoer@illinois.edu</a>> wrote:<o:p></o:p></span></p>
<div>
<div>
<p class="MsoNormal"><span style="color:black">Hi, I'm trying to follow the advice on building ParaView on Titan using the ParaViewSuperbuild method from an earlier discussion in June.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">When I run make in the "TOOLS" directory I get the following error:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">[ 66%] Building CXX object Utilities/ProcessXML/CMakeFiles/kwProcessXML.dir/ProcessXML.cxx.o<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">Linking CXX executable ../../bin/vtkkwProcessXML-pv4.0<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">/usr/bin/ld: attempted static link of dynamic object `../../lib/libvtkCommonCore-pv4.0.so.1'<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">collect2: error: ld returned 1 exit status<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">make[6]: *** [bin/vtkkwProcessXML-pv4.0] Error 1<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">make[5]: *** [Utilities/ProcessXML/CMakeFiles/kwProcessXML.dir/all] Error 2<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">make[4]: *** [CMakeFiles/pvCompileTools.dir/rule] Error 2<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">make[3]: *** [pvCompileTools] Error 2<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">CMake Error at /ccs/home/vanmoer/builds/superbuild/tools-build/pv-paraview-build.cmake:26 (message):<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> Failed!!!<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">make[2]: *** [paraview/src/paraview-stamp/paraview-build] Error 1<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">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.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">Any suggestions?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">Thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">Mark<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="color:black"><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><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>