<div><br>Hi,</div>
<div> </div>
<div>Thanks - Am I corect in assuming hardware rendering?</div>
<div> </div>
<div>I think I have finally fixed the problem - this is part of the patch from Kitware</div>
<div class="diff add">+ ELSE (DEFINED MPI_C_COMPILER)</div>
<div class="diff add">+ # Older MPI module</div>
<div class="diff add">+ MARK_AS_ADVANCED(CLEAR MPI_INCLUDE_PATH)</div>
<div class="diff add">+ MARK_AS_ADVANCED(CLEAR MPI_LIBRARY)</div>
<div class="diff add">+ MARK_AS_ADVANCED(CLEAR MPI_EXTRA_LIBRARY)</div>
<div class="diff add">+</div>
<div class="diff add">+ INCLUDE_DIRECTORIES(${MPI_INCLUDE_PATH})</div>
<div class="diff add">+ SET(ICET_MPI_LIBRARIES ${MPI_LIBRARY} ${MPI_EXTRA_LIBRARY})</div>
<div class="diff add">+ ENDIF(DEFINED MPI_C_COMPILER)</div>
<p> </p>
<div>I had to chage the last line which is </div>
<div>SET(ICET_MPI_LIBRARIES ${MPI_LIBRARY} ${MPI_EXTRA_LIBRARY})</div>
<div> </div>
<div>to the following</div>
<div>SET(ICET_MPI_LIBRARIES ${MPI_LIBRARY} ${MPI_C_LIBRARIES})</div>
<div> </div>
<div>What I am finding is that, otherwise the mpicxx does get linked and then when you do a gcc to compile it all breaks. Replacing gcc with g++ works OK as expected.</div>
<div> </div>
<div>I am not sure if this is required specifically for my set up here or is it a bug? </div>
<div> </div>
<div>Regards,</div>
<div>Rakesh</div>
<div><br></div>
<div class="gmail_quote">On 9 January 2012 15:26, David E DeMarle <span dir="ltr"><<a href="mailto:dave.demarle@kitware.com">dave.demarle@kitware.com</a>></span> wrote:<br>
<blockquote style="BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px 0.8ex;PADDING-LEFT:1ex" class="gmail_quote">ParaView depends on IceT for parallel rendering. If you don't have PARAVIEW_USE_PARALLEL on, or if you do by only intend to do parallel data processing (pvdataserver), then you don't need it, otherwise you do.
<div><span class="HOEnZb"><font color="#888888"></font></span>
<div>
<div><span class="HOEnZb"><font color="#888888"><br clear="all">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" value="+15188814909">518-881-4909</a></font></span>
<div>
<div class="h5"><br><br><br>
<div class="gmail_quote">On Mon, Jan 9, 2012 at 10:21 AM, Rakesh Hammond <span dir="ltr"><<a href="mailto:rakesh.hammond@googlemail.com" target="_blank">rakesh.hammond@googlemail.com</a>></span> wrote:<br>
<blockquote style="BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px 0.8ex;PADDING-LEFT:1ex" class="gmail_quote">
<div>Bruno,</div>
<div> </div>
<div>Thanks for your help - I got the latest CMakeLists.txt file for ICET and tried to build again (after blowing away my build directory). It breaks at the same place as before. On closer inspection, the link.txt file does appear to have links to mpicxx file, removing that and running the same line in the link.txt file builds the test fine.</div>
<div> </div>
<div>I am beginnning to wonder if some changes are required else where as well? Any pointeres anyone?</div>
<div> </div>
<div>On a different note, why does ParaView need IceT? </div>
<div> </div>
<div>I am tempted to turn it off if this action will have no adverse effects on our requirement.</div>
<div> </div>
<div>Regards,</div>
<div>Rakesh<br><br></div>
<div>
<div>
<div class="gmail_quote">On 9 January 2012 08:55, Bruno Santos <span dir="ltr"><<a href="mailto:bruno.santos@bluecape.com.pt" target="_blank">bruno.santos@bluecape.com.pt</a>></span> wrote:<br>
<blockquote style="BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px 0.8ex;PADDING-LEFT:1ex" class="gmail_quote">
<div bgcolor="#FFFFFF" text="#000000">Hi Rakesh,<br><br>Good thing you asked!<br><br>OK, so the bug tracker had the commit "number": 967348651061f039b3dbc7a71d70687d928977dd<br>So I went to the repository for ParaView on Github: <a href="https://github.com/Kitware/ParaView/" target="_blank">https://github.com/Kitware/ParaView/</a><br>
Clicked on one of the "commits" tab and replace "master" with the commit number: <a href="https://github.com/Kitware/ParaView/commits/master" target="_blank">https://github.com/Kitware/ParaView/commits/master</a> -> <a href="https://github.com/Kitware/ParaView/commits/967348651061f039b3dbc7a71d70687d928977dd" target="_blank">https://github.com/Kitware/ParaView/commits/967348651061f039b3dbc7a71d70687d928977dd</a><br>
So, since the problem was with IceT, I went to where it is in ParaView: <a href="https://github.com/Kitware/ParaView/tree/967348651061f039b3dbc7a71d70687d928977dd/Utilities" target="_blank">https://github.com/Kitware/ParaView/tree/967348651061f039b3dbc7a71d70687d928977dd/Utilities</a><br>
OK, the respective folder only says "IceT - 916f22d", namely the commit number from where it comes. Went to the root folder of ParaView and looked at ".gitmodules": <a href="https://github.com/Kitware/ParaView/blob/967348651061f039b3dbc7a71d70687d928977dd/.gitmodules" target="_blank">https://github.com/Kitware/ParaView/blob/967348651061f039b3dbc7a71d70687d928977dd/.gitmodules</a><br>
<br>OK, IceT repo is here: git://<a href="http://paraview.org/IceT.git" target="_blank">paraview.org/IceT.git</a> - so I jumped online to here: <a href="http://paraview.org/IceT.git" target="_blank">paraview.org/IceT.git</a> -- automatic redirect by the website --> <a href="http://paraview.org/gitweb?p=IceT.git" target="_blank">http://paraview.org/gitweb?p=IceT.git</a><br>
Clicked on one of the links that say "commit" and replace the number by "916f22d": <a href="http://paraview.org/gitweb?p=IceT.git;a=commit;h=916f22d" target="_blank">paraview.org/gitweb?p=IceT.git;a=commit;h=916f22d</a><br>
Mmm, it's a merge. OK, then clicked on the "shortlog" link and this <i>jumped out</i> of the list: <a href="http://paraview.org/gitweb?p=IceT.git;a=commit;h=36fad20880740ecacedf9cf80f92a3255c19055b" target="_blank">http://paraview.org/gitweb?p=IceT.git;a=commit;h=36fad20880740ecacedf9cf80f92a3255c19055b</a><br>
Clicked on the "diff" link and there we have it!<br><br>Wait, I found another commit different from the one I indicated before. Apparently I didn't backtrack it properly.... Oh, both are from the same day! So both are needed! See the shortlog: <a href="http://paraview.org/gitweb?p=IceT.git;a=shortlog;h=e2231f1454c90d7d4fd16540d9468ffbdaaec3f7" target="_blank">http://paraview.org/gitweb?p=IceT.git;a=shortlog;h=e2231f1454c90d7d4fd16540d9468ffbdaaec3f7</a><br>
<br>Best regards,<br>Bruno
<div>
<div><br><br>On 07-01-2012 21:31, Rakesh Hammond wrote: </div></div>
<blockquote type="cite">
<div>
<div>Bruno,<br><br>Thanks - I think this is what I am after, I will have a play with this diff.<br><br>For future reference, can you please tell me how did you find it? <br><br>I think it would be nice to have a link from the mantis ticket to source code change !<br>
<br>Regards,<br>Rakesh<br>
<div class="gmail_quote">On 7 January 2012 19:59, Bruno Santos <span dir="ltr"><<a href="mailto:bruno.santos@bluecape.com.pt" target="_blank">bruno.santos@bluecape.com.pt</a>></span> wrote:<br>
<blockquote style="BORDER-LEFT:rgb(204,204,204) 1px solid;MARGIN:0pt 0pt 0pt 0.8ex;PADDING-LEFT:1ex" class="gmail_quote">Hi Rakesh,<br><br>If I backtracked it correctly, this should be the fix you are looking for:<br><a href="http://paraview.org/gitweb?p=IceT.git;a=commitdiff;h=e2231f1454c90d7d4fd16540d9468ffbdaaec3f7" target="_blank">http://paraview.org/gitweb?p=IceT.git;a=commitdiff;h=e2231f1454c90d7d4fd16540d9468ffbdaaec3f7</a><br>
<br>Best regards,<br>Bruno<br><br>Date: Sat, 7 Jan 2012 12:07:24 +0000<br>From: Rakesh Hammond <<a href="mailto:rakesh.hammond@googlemail.com" target="_blank">rakesh.hammond@googlemail.com</a>><br>Subject: [Paraview] Icet test build fails with Paraview-3.12.0<br>
<div>
<div><br>Hi,<br><br>I am trying to build the ParaView-3.12.0 (stable release on 08th of<br>November 2011) with an mpich library on Linux with gcc-4.5.2.<br><br>The IceT tests unfortunately fails. Having looked around the bug tracker,<br>
I found this ticket<br><br><a href="http://www.vtk.org/Bug/view.php?id=12716" target="_blank">http://www.vtk.org/Bug/view.php?id=12716</a><br><br>The problem I am having is same as what is described here, unfortunately<br>
the fix was merged into the current development directory on the 11th of<br>November 2011.<br><br>Is it possible to find out exactly what the fix was ? (for example doing a<br>commitdif?). I am not familiar with git that much, but looking around I was<br>
unable to get the code difference. If any one knows how to get the<br>changes, please send me the url link.<br><br>Is there are any plans to release a patch for 3.12.0 any time soon? At<br>work, we are not allowed to build from nightly builds, so I am a little bit<br>
stuck on how to progress further. My options are either to wait for a<br>patch or make the necessary modifications for the stable 3.12.0 and build.<br><br>Thanks,<br>Rakesh<br><br></div></div>_______________________________________________<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>
</blockquote></div><br></div></div>
<p align="left" color="#000000">Não foram detectados vírus nesta mensagem.<br>Verificado por AVG - <a href="http://www.avg.com/" target="_blank">www.avg.com</a><br>Versão: 2012.0.1901 / Base de dados de Vírus: 2109/4731 - Data de Lançamento: 01/08/12</p>
<span><font color="#888888"></font></span></blockquote><span><font color="#888888"><br><br><pre cols="72">--
<a href="http://www.bluecape.com.pt/" target="_blank">http://www.bluecape.com.pt</a>
blueCAPE Lda - CAE solutions
Rua Fonte dos Corvos, n.29
Casais da Serra
2665-305 Milharado
PORTUGAL
<a href="tel:%28%2B351%29%20219%20755%20345" target="_blank" value="+351219755345">(+351) 219 755 345</a> Tel.
<a href="tel:%28%2B351%29%20219%20755%20345" target="_blank" value="+351219755345">(+351) 219 755 345</a> Fax
<a href="tel:%28%2B351%29%20963%20440%20984" target="_blank" value="+351963440984">(+351) 963 440 984</a> Mob.
</pre></font></span></div></blockquote></div><br></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></blockquote></div><br>