<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" value="+15188814909" target="_blank">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 class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
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>