<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 9.00.8112.16440"></HEAD>
<BODY>
<DIV dir=ltr align=left><FONT face=Arial><FONT color=#0000ff><FONT
size=2>David<SPAN class=622073820-11012012> Partyka pointed me to
ExecuteProtoC.cmake.in and I managed to work it out from
there...</SPAN></FONT></FONT></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN
class=622073820-11012012></SPAN></FONT></FONT></FONT> </DIV>
<DIV dir=ltr align=left><SPAN class=438384002-10012012></SPAN></DIV>
<DIV dir=ltr align=left><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN
class=438384002-10012012>not sure if it is a bug but <SPAN
class=622073820-11012012>the</SPAN></SPAN><SPAN class=438384002-10012012> cause
of the problem was an introduction of "/usr/lib64" at the beginning of the
LD_LIBRARY_PATH</SPAN></FONT></FONT></FONT></DIV>
<DIV dir=ltr align=left><SPAN class=438384002-10012012><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=438384002-10012012><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=438384002-10012012><FONT color=#0000ff
size=2 face=Arial>I found that this line in the ExecuteProtoC.cmake.in caused it
and if I commented it out the build progressed</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=438384002-10012012><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=438384002-10012012><FONT color=#0000ff
size=2 face=Arial># get_filename_component(PYTHON_LIB "@PYTHON_LIBRARY@"
PATH)</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=438384002-10012012><FONT color=#0000ff
size=2 face=Arial> </DIV></FONT></SPAN>
<DIV dir=ltr align=left><SPAN class=438384002-10012012><FONT color=#0000ff
size=2 face=Arial>Looking at my overall build config though, I see this is what
cmake has auto-populated the PYTHON_LIBRARY variable with<SPAN
class=622073820-11012012> this</SPAN> (although everything else is found in
the right spot).</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=438384002-10012012><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=438384002-10012012><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN></DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial>PYTHON_EXECUTABLE
/usr/local/python/2.7.1-gcc/bin/python2.7<BR>PYTHON_EXTRA_LIBS<BR>PYTHON_INCLUDE_DIR
/usr/local/python/2.7.1-gcc/include/python2.7<BR>PYTHON_LIBRARY
/usr/lib64/libpython2.4.so</FONT></DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial></FONT></DIV>
<DIV dir=ltr align=left><SPAN class=438384002-10012012><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=438384002-10012012><FONT color=#0000ff
size=2 face=Arial>If I set PYTHON_LIBRARY to
/usr/local/python/2.7.1-gcc/lib/libpython2.7.so, the build will also
complete<SPAN class=622073820-11012012>d</SPAN> (even with the above
get_filename_component).</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=438384002-10012012><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=438384002-10012012><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=438384002-10012012><FONT color=#0000ff
size=2 face=Arial>So possible issues:</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=438384002-10012012><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=438384002-10012012><FONT color=#0000ff
size=2 face=Arial>1) get_filename_component(PYTHON_LIB "@PYTHON_LIBRARY@" PATH)
is not required</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=438384002-10012012><FONT color=#0000ff
size=2 face=Arial>2) There is an issue with the cmake python library dependency
search</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=438384002-10012012><FONT color=#0000ff
size=2 face=Arial>3) I mucked something up</FONT></SPAN></DIV><FONT
color=#0000ff size=2 face=Arial></FONT>
<DIV dir=ltr align=left><BR><SPAN class=438384002-10012012></SPAN><FONT
face=Arial><FONT color=#0000ff><FONT size=2>C<SPAN
class=438384002-10012012>heers,</SPAN></FONT></FONT></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN
class=438384002-10012012></SPAN></FONT></FONT></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN
class=438384002-10012012></SPAN></FONT></FONT></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN
class=438384002-10012012>Paul</SPAN></FONT></FONT></FONT></DIV><BR>
<DIV dir=ltr lang=en-us class=OutlookMessageHeader align=left>
<HR tabIndex=-1>
<FONT size=2 face=Tahoma><B>From:</B> David E DeMarle
[mailto:dave.demarle@kitware.com] <BR><B>Sent:</B> Thursday, 12 January 2012
12:22 AM<BR><B>To:</B> Paul McIntosh<BR><B>Cc:</B> Biddiscombe, John A.;
paraview@paraview.org<BR><B>Subject:</B> Re: [Paraview] 3.12.0 building issues
due to Protobuf<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV>I doubt that we have any in-built support for using an external protobuf,
but like all other pv/vtk dependencies, it would be great to have as an option
if anyone has the time to make it happen.</DIV>
<DIV><BR></DIV>My altercations with protobuf had to do with cross compilation on
Cray. I don't recall if the error/warning messages were similar. The overall
strategy of cross compilation is to build ParaView once for the front end and
then use the generated compile time executables (such as protoc) during the back
end compile. My changes had to do with making that work right and you can
find them in the git log for ParaView's protobuf submodule.
<DIV>
<DIV>
<DIV>
<DIV><BR></DIV>
<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"
target=_blank value="+15188814909">518-881-4909</A><BR><BR><BR>
<DIV class=gmail_quote>On Mon, Jan 9, 2012 at 7:05 PM, Paul McIntosh <SPAN
dir=ltr><<A href="mailto:paul.mcintosh@internetscooter.com"
target=_blank>paul.mcintosh@internetscooter.com</A>></SPAN> wrote:<BR>
<BLOCKQUOTE
style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>Thanks John,<BR><BR>I couldn't find any libstdc++ lib
lurking anywhere.<BR><BR>With a bit more investigation it looks like the
"protoc" compiler is built<BR>correctly, however when it is called on to build
some protocols it is not<BR>finding the libraries it was built with. So the
protoc step fails and<BR>therefore the rest of the build fails as it requires
the output of protoc.<BR><BR>I can reproduce the problem externally by
unsetting and setting paths, I<BR>just need to work out how it is called in
the cmake build and how to force<BR>it to use the correct
environment.<BR><BR>Cheers,<BR><BR>Paul<BR>
<DIV>
<DIV><BR>-----Original Message-----<BR>From: Biddiscombe, John A. [mailto:<A
href="mailto:biddisco@cscs.ch" target=_blank>biddisco@cscs.ch</A>]<BR>Sent:
Friday, 23 December 2011 9:15 PM<BR>To: Paul McIntosh; <A
href="mailto:paraview@paraview.org"
target=_blank>paraview@paraview.org</A><BR>Subject: RE: [Paraview] 3.12.0
building issues due to Protobuf<BR><BR>I had a very similar problem on our
cray (i.e. same error message), but it<BR>was not caused by protobuf.<BR>We
have the standard libs in /usr/lib64, but when using icc/ifort
the<BR>libstdc++ lib from /opt/cray/blah/blah/something something should be
linked<BR>and not the one from /usr/lib64<BR><BR>Have a look and see if there
is another libstdc++ in a special gcc/4.4.5 dir<BR>somewhere - since you're
using gcc (I was using icc) it may not be
so<BR>trivial.<BR><BR>JB<BR><BR>-----Original Message-----<BR>From: <A
href="mailto:paraview-bounces@paraview.org"
target=_blank>paraview-bounces@paraview.org</A> [mailto:<A
href="mailto:paraview-bounces@paraview.org"
target=_blank>paraview-bounces@paraview.org</A>]<BR>On Behalf Of Paul
McIntosh<BR>Sent: 22 December 2011 03:48<BR>To: <A
href="mailto:paraview@paraview.org"
target=_blank>paraview@paraview.org</A><BR>Subject: [Paraview] 3.12.0 building
issues due to Protobuf<BR><BR>Hi All,<BR><BR>Just wondering if anyone has come
across this problem and worked around it?<BR><BR>I am using modules and have
the following configuration where I have<BR>protobuf built and available in
/usr/local/protobuf/2.4.1<BR><BR>Currently Loaded Modulefiles:<BR> 1)
gmp/4.3.1 3) gcc/4.4.5
5) qt/4.6.2
7)<BR>virtualgl/2.2.90 9) cmake/2.8.3<BR> 2)
mpfr/2.4.2 4) openmpi-gcc/1.4.3 6)
python/2.7.1-gcc 8)<BR>paraview/3.10.1 10)
protobuf/2.4.1<BR><BR>The ParaView protobuf build seems to be doing everything
on it's own,<BR>ignoring compiler paths, prebuilt libraries etc, with no cmake
options<BR>except for switching on and off tests. So everything else builds
but I get<BR>stuck below.<BR><BR>[ 84%] Generating vtkPVMessage.pb.h, <A
href="http://vtkPVMessage.pb.cc"
target=_blank>vtkPVMessage.pb.cc</A><BR>/usr/local/src/PARAVIEW/3.12.0/ParaView-Build/bin/protoc:<BR>/usr/lib64/libstdc++.so.6:
version `GLIBCXX_3.4.10' not found (required
by<BR>/usr/local/src/PARAVIEW/3.12.0/ParaView-Build/bin/libprotobuf.so)<BR>/usr/local/src/PARAVIEW/3.12.0/ParaView-Build/bin/protoc:<BR>/usr/lib64/libstdc++.so.6:
version `GLIBCXX_3.4.10' not found (required
by<BR>/usr/local/src/PARAVIEW/3.12.0/ParaView-Build/bin/libprotoc.so)<BR>/usr/local/src/PARAVIEW/3.12.0/ParaView-Build/bin/protoc:<BR>/usr/lib64/libstdc++.so.6:
version `GLIBCXX_3.4.9' not found (required
by<BR>/usr/local/src/PARAVIEW/3.12.0/ParaView-Build/bin/libprotoc.so)<BR>/usr/local/src/PARAVIEW/3.12.0/ParaView-Build/bin/protoc:<BR>/usr/lib64/libstdc++.so.6:
version `GLIBCXX_3.4.11' not found (required
by<BR>/usr/local/src/PARAVIEW/3.12.0/ParaView-Build/bin/libprotoc.so)<BR>[
84%] Built target protobuf_code_generation [ 84%] Building CXX
object<BR>ParaViewCore/ServerImplementation/CMakeFiles/vtkPVServerImplementation.dir/v<BR>tkPVSessionBase.cxx.o<BR>In
file included
from<BR>/usr/local/src/PARAVIEW/3.12.0/ParaView-3.12.0/ParaViewCore/ServerImplementa<BR>tion/vtkPVSessionBase.cxx:22:<BR>/usr/local/src/PARAVIEW/3.12.0/ParaView-3.12.0/ParaViewCore/ServerImplementa<BR>tion/vtkSMMessage.h:30:29:
error: vtkPVMessage.pb.h: No such file or<BR>directory In file included
from<BR>/usr/local/src/PARAVIEW/3.12.0/ParaView-3.12.0/ParaViewCore/ServerImplementa<BR>tion/vtkPVSessionBase.cxx:22:<BR>/usr/local/src/PARAVIEW/3.12.0/ParaView-3.12.0/ParaViewCore/ServerImplementa<BR>tion/vtkSMMessage.h:38:
error: expected unqualified-id before â&â
token<BR>/usr/local/src/PARAVIEW/3.12.0/ParaView-3.12.0/ParaViewCore/ServerImplementa<BR>tion/vtkSMMessage.h:38:
error: expected â)â before â&â
token<BR>/usr/local/src/PARAVIEW/3.12.0/ParaView-3.12.0/ParaViewCore/ServerImplementa<BR>tion/vtkSMMessage.h:38:
error: expected initializer before â&â token<BR>make[2]:
***<BR>[ParaViewCore/ServerImplementation/CMakeFiles/vtkPVServerImplementation.dir/<BR>vtkPVSessionBase.cxx.o]
Error 1<BR>make[1]:
***<BR>[ParaViewCore/ServerImplementation/CMakeFiles/vtkPVServerImplementation.dir/<BR>all]
Error 2<BR>make: *** [all] Error 2<BR><BR>Any
hints?<BR><BR>Cheers,<BR><BR>Paul<BR>---<BR><A
href="http://www.internetscooter.com"
target=_blank>www.internetscooter.com</A><BR><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<BR><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:<BR><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>_______________________________________________<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></DIV></DIV></BLOCKQUOTE></DIV><BR></DIV></DIV></DIV></DIV></BODY></HTML>