Hi Utkarsh, The patch works partially. Both sequential and parallel builds are possible now, but only when not compiling against Mesa (and using VTK_USE_RPATH:BOOL=OFF). If one does, creating the help file fails, even though the mesa lib directory is part of my LD_LIBRARY_PATH:
> /usr/bin/cmake -E cmake_progress_report > /data/ParaView3_Git_Build_SLES10_SP2/CMakeFiles > [ 99%] Creating Documentation for ParaViewSources > cd /data/ParaView3_Git_Build_SLES10_SP2/Servers/ServerManager && > /usr/bin/cmake > -DfullXMLFile=/data/ParaView3_Git/Applications/ParaView/ParaViewSources.xml > -P > /data/ParaView3_Git_Build_SLES10_SP2/CMake/ExecuteSMExtractDocumentation.cmake > /data/ParaView3_Git_Build_SLES10_SP2/bin/vtkSMExtractDocumentation-real: > error while loading shared libraries: libOSMesa.so.7: cannot open shared > object file: No such file or directory > /usr/bin/cmake -E cmake_progress_report > /data/ParaView3_Git_Build_SLES10_SP2/CMakeFiles > [ 99%] Creating Documentation for ParaViewFilters > cd /data/ParaView3_Git_Build_SLES10_SP2/Servers/ServerManager && > /usr/bin/cmake > -DfullXMLFile=/data/ParaView3_Git/Applications/ParaView/ParaViewFilters.xml > -P > /data/ParaView3_Git_Build_SLES10_SP2/CMake/ExecuteSMExtractDocumentation.cmake > /data/ParaView3_Git_Build_SLES10_SP2/bin/vtkSMExtractDocumentation-real: > error while loading shared libraries: libOSMesa.so.7: cannot open shared > object file: No such file or directory Sven Utkarsh Ayachit wrote, On 20.04.2010 17:02: > Sven, > > Attached is a patch that may resolve this issue. Can you give it a try? > > Thanks > Utkarsh > > On Tue, Apr 20, 2010 at 7:49 AM, Sven Buijssen > <[email protected]> wrote: >> Hi Paul, >> >>> Sven Buijssen wrote: >>>> (off the list for the moment while discussing some technical details) >>>> >>> [taking back to the list] >>>> I managed to compile PV 3.8 RC1 >>>> (http://www.paraview.org/files/v3.8/ParaView-3.8.0-RC1.tar.gz) on a >>>> 32bit openSuSE 11.1 system, with any of cmake 2.6.4, 2.8.0 and 2.8.1. >>>> Here's my recipe: >>>> >>>> [...] >>>> >>>> % make -j 16 >>>> >>> >>> Ouch, just for fun I tried to use make -j 2 instead of a single process >>> make and the problem went away, i.e. the compile succeeded. That's not >>> very good... >>> Out of interest, do you always build multi-process? I'm on a dual-core >>> machine and when building in the background make -j N isn't very >>> attractive. >> >> Yes, I usually build with N > 1. >> I just tested your hypothesis and I can confirm that (for a clean build) >> it does make a difference whether one compiles with 1 or more processes. >> The error > make[2]: *** No rule to make target >> `Applications/ParaView/../../Documentation/paraview.qch', needed by >> `Applications/ParaView/qrc_paraview_help.cxx'. Stop. >> does only occur when compiling sequentially (on 32 bit Linux). Funny to >> see that on my 3 different 64 bit Linux operating systems compilation >> always fails at this point, even with N > 1. >> >> Sven >> _______________________________________________ >> 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
