[Paraview] 3.12.0 building issues due to Protobuf

Paul McIntosh paul.mcintosh at internetscooter.com
Wed Jan 11 15:41:03 EST 2012 

David Partyka pointed me to ExecuteProtoC.cmake.in and I managed to work it
out from there...
 
not sure if it is a bug but the cause of the problem was an introduction of
"/usr/lib64" at the beginning of the LD_LIBRARY_PATH
 
I found that this line in the ExecuteProtoC.cmake.in caused it and if I
commented it out the build progressed
 
# get_filename_component(PYTHON_LIB "@PYTHON_LIBRARY@" PATH)
 
Looking at my overall build config though, I see this is what cmake has
auto-populated the PYTHON_LIBRARY variable with this (although everything
else is found in the right spot).
 
PYTHON_EXECUTABLE /usr/local/python/2.7.1-gcc/bin/python2.7
PYTHON_EXTRA_LIBS
PYTHON_INCLUDE_DIR /usr/local/python/2.7.1-gcc/include/python2.7
PYTHON_LIBRARY /usr/lib64/libpython2.4.so
 
If I set PYTHON_LIBRARY to /usr/local/python/2.7.1-gcc/lib/libpython2.7.so,
the build will also completed (even with the above get_filename_component).
 
So possible issues:
1) get_filename_component(PYTHON_LIB "@PYTHON_LIBRARY@" PATH) is not
required
2) There is an issue with the cmake python library dependency search
3) I mucked something up

Cheers,
 
Paul

  _____  

From: David E DeMarle [mailto:dave.demarle at kitware.com] 
Sent: Thursday, 12 January 2012 12:22 AM
To: Paul McIntosh
Cc: Biddiscombe, John A.; paraview at paraview.org
Subject: Re: [Paraview] 3.12.0 building issues due to Protobuf


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.

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. 

David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909



On Mon, Jan 9, 2012 at 7:05 PM, Paul McIntosh
<paul.mcintosh at internetscooter.com> wrote:


Thanks John,

I couldn't find any libstdc++ lib lurking anywhere.

With a bit more investigation it looks like the "protoc" compiler is built
correctly, however when it is called on to build some protocols it is not
finding the libraries it was built with. So the protoc step fails and
therefore the rest of the build fails as it requires the output of protoc.

I can reproduce the problem externally by unsetting and setting paths, I
just need to work out how it is called in the cmake build and how to force
it to use the correct environment.

Cheers,

Paul


-----Original Message-----
From: Biddiscombe, John A. [mailto:biddisco at cscs.ch]
Sent: Friday, 23 December 2011 9:15 PM
To: Paul McIntosh; paraview at paraview.org
Subject: RE: [Paraview] 3.12.0 building issues due to Protobuf

I had a very similar problem on our cray (i.e. same error message), but it
was not caused by protobuf.
We have the standard libs in /usr/lib64, but when using icc/ifort the
libstdc++ lib from /opt/cray/blah/blah/something something should be linked
and not the one from /usr/lib64

Have a look and see if there is another libstdc++ in a special gcc/4.4.5 dir
somewhere - since you're using gcc (I was using icc) it may not be so
trivial.

JB

-----Original Message-----
From: paraview-bounces at paraview.org [mailto:paraview-bounces at paraview.org]
On Behalf Of Paul McIntosh
Sent: 22 December 2011 03:48
To: paraview at paraview.org
Subject: [Paraview] 3.12.0 building issues due to Protobuf

Hi All,

Just wondering if anyone has come across this problem and worked around it?

I am using modules and have the following configuration where I have
protobuf built and available in /usr/local/protobuf/2.4.1

Currently Loaded Modulefiles:
 1) gmp/4.3.1           3) gcc/4.4.5           5) qt/4.6.2            7)
virtualgl/2.2.90    9) cmake/2.8.3
 2) mpfr/2.4.2          4) openmpi-gcc/1.4.3   6) python/2.7.1-gcc    8)
paraview/3.10.1    10) protobuf/2.4.1

The ParaView protobuf build seems to be doing everything on it's own,
ignoring compiler paths, prebuilt libraries etc, with no cmake options
except for switching on and off tests. So everything else builds but I get
stuck below.

[ 84%] Generating vtkPVMessage.pb.h, vtkPVMessage.pb.cc
/usr/local/src/PARAVIEW/3.12.0/ParaView-Build/bin/protoc:
/usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.10' not found (required by
/usr/local/src/PARAVIEW/3.12.0/ParaView-Build/bin/libprotobuf.so)
/usr/local/src/PARAVIEW/3.12.0/ParaView-Build/bin/protoc:
/usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.10' not found (required by
/usr/local/src/PARAVIEW/3.12.0/ParaView-Build/bin/libprotoc.so)
/usr/local/src/PARAVIEW/3.12.0/ParaView-Build/bin/protoc:
/usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.9' not found (required by
/usr/local/src/PARAVIEW/3.12.0/ParaView-Build/bin/libprotoc.so)
/usr/local/src/PARAVIEW/3.12.0/ParaView-Build/bin/protoc:
/usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.11' not found (required by
/usr/local/src/PARAVIEW/3.12.0/ParaView-Build/bin/libprotoc.so)
[ 84%] Built target protobuf_code_generation [ 84%] Building CXX object
ParaViewCore/ServerImplementation/CMakeFiles/vtkPVServerImplementation.dir/v
tkPVSessionBase.cxx.o
In file included from
/usr/local/src/PARAVIEW/3.12.0/ParaView-3.12.0/ParaViewCore/ServerImplementa
tion/vtkPVSessionBase.cxx:22:
/usr/local/src/PARAVIEW/3.12.0/ParaView-3.12.0/ParaViewCore/ServerImplementa
tion/vtkSMMessage.h:30:29: error: vtkPVMessage.pb.h: No such file or
directory In file included from
/usr/local/src/PARAVIEW/3.12.0/ParaView-3.12.0/ParaViewCore/ServerImplementa
tion/vtkPVSessionBase.cxx:22:
/usr/local/src/PARAVIEW/3.12.0/ParaView-3.12.0/ParaViewCore/ServerImplementa
tion/vtkSMMessage.h:38: error: expected unqualified-id before â&â token
/usr/local/src/PARAVIEW/3.12.0/ParaView-3.12.0/ParaViewCore/ServerImplementa
tion/vtkSMMessage.h:38: error: expected â)â before â&â token
/usr/local/src/PARAVIEW/3.12.0/ParaView-3.12.0/ParaViewCore/ServerImplementa
tion/vtkSMMessage.h:38: error: expected initializer before â&â token
make[2]: ***
[ParaViewCore/ServerImplementation/CMakeFiles/vtkPVServerImplementation.dir/
vtkPVSessionBase.cxx.o] Error 1
make[1]: ***
[ParaViewCore/ServerImplementation/CMakeFiles/vtkPVServerImplementation.dir/
all] Error 2
make: *** [all] Error 2

Any hints?

Cheers,

Paul
---
www.internetscooter.com

_______________________________________________
Powered by www.kitware.com

Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at:
http://paraview.org/Wiki/ParaView

Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview

_______________________________________________
Powered by www.kitware.com

Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at:
http://paraview.org/Wiki/ParaView

Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.paraview.org/pipermail/paraview/attachments/20120112/93501ead/attachment-0001.htm>

More information about the ParaView mailing list