[Paraview] paraview installation error

[David E DeMarle]

Sorry, nothing comes to my mind after looking at the config, other than it
is possible that the build system got confused and you should try a clean
build in a new build directory. When you do, please save off the entire
build output (make -j 1>& buildout.txt&; tail -f buildout.txt) so that we
can see what happens when vtkFiltersParallelMPI is built and later wrapped
into ParaView's client server (CS) control language.



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


On Tue, Mar 12, 2013 at 12:02 PM, Pradeep Jha <
pradeep at ccs.engg.nagoya-u.ac.jp> wrote:

> Thanks for the response. I am attaching the CMakeCache.txt file with this
> email.
>
>
> 2013/3/12 David E DeMarle <dave.demarle at kitware.com>
>
>> These look like two separate issues to me.
>>
>> On Tue, Mar 12, 2013 at 1:40 AM, Pradeep Jha <
>> pradeep at ccs.engg.nagoya-u.ac.jp> wrote:
>>
>>> I am trying to install Paraview on a supercomputer with OSMesa support.
>>> I have installed OSMesa and everything else required and set my
>>> configurations according to this page<http://paraview.org/Wiki/ParaView/Users_Guide/Parallel_Rendering#Offscreen_Software_Rendering_via_OSMesa>in the cmake file.
>>>
>>> The only thing is I cannot find the libGLU.so on the computer. To
>>> install the libGLU, when I use the rpm file, I get the following output:
>>>
>>> ----------------------------------------------------------------------------
>>> [k00603 at fe01p08 HH-1298]$rpm2cpio
>>> /home/hp120242/k00603/distfiles/HH-1298/mesa-libGLU-6.5.1-7.10.el5.x86_64.rpm
>>> | cpio -id
>>> cpio: ./usr/lib64/libGLU.so.1 not created: newer or same age version
>>> exists
>>> cpio: ./usr/lib64/libGLU.so.1.3.060501 not created: newer or same age
>>> version exists
>>> 1026 blocks
>>>
>>> ----------------------------------------------------------------------------
>>>
>>> When I did:
>>> ---------------------------------------------------------------
>>> [k00603 at fe01p09 ~]$locate libGLU
>>> /usr/lib/libGLU.so.1
>>> /usr/lib/libGLU.so.1.3.060501
>>> /usr/lib64/libGLU.so.1
>>> /usr/lib64/libGLU.so.1.3.060501
>>>  ----------------------------------------------------
>>> so I set the "OPENGL_glu_LIBRARY" environment to
>>> "/usr/lib64/libGLU.so.1" and generate the Makefile using Cmake.
>>>
>>>
>> That seems like it should be fine. The RPM is just telling you that you
>> already have a GLU.
>> FWIW: Personally I've always just downloaded Mesa source and built it
>> myself locally rather than using the package manager to install it for
>> everyone. Doing so I'm sure to use the libGLU that comes with mesa.
>>
>>
>> After this when I run the "make" command, I am getting the following
>>> error:
>>>
>>> --------------------------------------------------------------------------------------------------------
>>> [ 87%] Built target vtkRenderingMatplotlibCS
>>> [ 88%] Built target vtkPVServerManagerRenderingCS
>>> [ 89%] Built target vtkRenderingLODCS
>>> [ 90%] Built target vtkPVServerManagerDefaultCS
>>> Linking CXX shared library ../../../lib/
>>> libvtkPVServerManagerApplication-pv3.98.so<http://libvtkpvservermanagerapplication-pv3.98.so/>
>>> CMakeFiles/vtkPVServerManagerApplication.dir/vtkInitializationHelper.cxx.o:
>>> In function `PARAVIEW_CSSTREAMS_INITIALIZE(vtkClientServerInterpreter*)':
>>> vtkInitializationHelper.cxx:(.text+0x355): undefined reference to
>>> `vtkFiltersParallelMPICS_Initialize'
>>> collect2: ld returned 1 exit status
>>> make[2]: *** [lib/libvtkPVServerManagerApplication-pv3.98.so.1] Error 1
>>> make[1]: ***
>>> [ParaViewCore/ServerManager/SMApplication/CMakeFiles/vtkPVServerManagerApplication.dir/all]
>>> Error 2
>>> make: *** [all] Error 2
>>> ----------------------------------------------------
>>> ----------------------------------------------------
>>>
>>>
>> This error is entirely different and doesn't have anything to do with
>> Mesa. It is saying that the vtk library vtkFiltersParallelMPI isn't right.
>> Are you using an external VTK by any chance, and one without MPI turned on
>> in cmake? If so, don't. The ability to use an external VTK, rather than the
>> one that comes inside VTK is still brand new in ParaView 3.98. If not, can
>> you send me the CMakeCache.txt in you build tree? I might be able to spot
>> what is wrong from that.
>>
>>
>>> Any ideas what am I doing wrong?
>>>
>>> _______________________________________________
>>> 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/20130313/5b84d777/attachment-0001.htm>