CFD Online Discussion Forums

CFD Online Discussion Forums (http://www.cfd-online.com/Forums/)
-   OpenFOAM Installation (http://www.cfd-online.com/Forums/openfoam-installation/)
-   -   paraview 3.10.1 compiling error (1.6-ext) (http://www.cfd-online.com/Forums/openfoam-installation/92853-paraview-3-10-1-compiling-error-1-6-ext.html)

vkrastev September 27, 2011 10:19

paraview 3.10.1 compiling error (1.6-ext)
 
Hi everyone,
has anybody succeeded in solving the following compiling error (it comes at the end of the Allmake script run into the ThirdParty directory of OpenFOAM-1.6-EXT)?

CMake Error at /home/chuang/OpenFOAM/OpenFOAM-1.6-ext/ThirdParty/rpmBuild/BUILD/ParaView-3.10.1/CMake/BundleUtilities.cmake:627 (message):
error: fixup_bundle: not a valid bundle
Call Stack (most recent call first):
Applications/ParaView/cmake_install.cmake:80 (fixup_bundle)
Applications/cmake_install.cmake:37 (INCLUDE)
cmake_install.cmake:118 (INCLUDE)

Searching in the web I've found this post:

http://comments.gmane.org/gmane.comp...iew.user/11668

I've tried to turn off this option (it's in the /rpmBuild/BUILD/ParaView-3.10.1/CMake/ParaViewCommon.cmake file), but it seems like it is again turned on by some kind of default setting, because after turned it off the compilation stops again at the same point and opening back the ParaViewCommon.cmake file it appears again as the default version...

Any help will be appreciated

V.

PS-Has anybody succeeded AT ALL in compiling paraview 3.10.1 inside the 1.6-ext release?????

vkrastev September 28, 2011 07:15

Do I have to understand that all the 1.6-ext users do not use the ThirdParty-compiled paraview 3.10.1 for postprocessing?

V.:confused:

elvis September 29, 2011 05:07

Hi,

looks like most of the users dealing with Extend-Version go to "extend-project"

http://www.extend-project.de/user-fo...n-openfoam#286

vkrastev September 29, 2011 05:45

Quote:

Originally Posted by elvis (Post 326040)
Hi,

looks like most of the users dealing with Extend-Version go to "extend-project"

http://www.extend-project.de/user-fo...n-openfoam#286

Thanks for the reply, but unfortunately the discussion pointed by your link doesn't solve my problem. Maybe I could start a tread over there and see what happens...

Regards

V.

JulytoNovember September 30, 2011 11:42

I had the same problem, I switched to paraview-3.8.1 and now paraview works. Find your paraview.spec file its in the ThirdParty/rpmBuild/SPECS folder. Rename the file to Paraview-3.8.1, and also change all the 3.10.1 to 3.8.1 inside the file. This should work, I had to adjust and few things afterward, but they were not a big deal. Any further problem post here all I will see if I can help.

vkrastev September 30, 2011 11:48

Quote:

Originally Posted by JulytoNovember (Post 326275)
I had the same problem, I switched to paraview-3.8.1 and now paraview works. Find your paraview.spec file its in the ThirdParty/rpmBuild/SPECS folder. Rename the file to Paraview-3.8.1, and also change all the 3.10.1 to 3.8.1 inside the file. This should work, I had to adjust and few things afterward, but they were not a big deal. Any further problem post here all I will see if I can help.

Thanks for your hints, I think I will give them a try (and let you know what happens).

V.

vkrastev October 10, 2011 05:01

Quote:

Originally Posted by JulytoNovember (Post 326275)
I had the same problem, I switched to paraview-3.8.1 and now paraview works. Find your paraview.spec file its in the ThirdParty/rpmBuild/SPECS folder. Rename the file to Paraview-3.8.1, and also change all the 3.10.1 to 3.8.1 inside the file. This should work, I had to adjust and few things afterward, but they were not a big deal. Any further problem post here all I will see if I can help.

I switched to paraview 3.8.1 and now it works! Thanks once again!

V.

blaise October 28, 2011 03:17

fixed bundle problem solution
 
Hello,

I managed to fix the problem with the fixup_bundle issue following another post (I can't remember the link).

So: In the ParaView3.10.1 SPECS file (in ThirdParty/rpmbuild/SPECS) I added/altered some lines after

...
echo " _mesaLibPath : %{_mesaLibPath}"
echo " _pythonLibPath : %{_pythonLibPath}"
echo ""
set -x


# For Python and MPI Support (by the way, you need this to be added explicitly to
# compile PYTHON shell and parallel support into ParaView. The entries earlier in this file
# are not sufficient in my case)
addCMakeVariable PARAVIEW_ENABLE_PYTHON:BOOL=ON
addCMakeVariable PARAVIEW_USE_MPI:BOOL=ON

# >>> Here comes the fixup_bundle solution
addCMakeVariable PARAVIEW_INSTALL_THIRD_PARTY_LIBRARIES:BOOL=OFF

# start with these general settings
addCMakeVariable VTK_USE_TK:BOOL=OFF

# >>> I think one this is necessary too.
addCMakeVariable BUILD_SHARED_LIBS:BOOL=OFF VTK_USE_RPATH:BOOL=OFF
#addCMakeVariable BUILD_SHARED_LIBS:BOOL=ON VTK_USE_RPATH:BOOL=OFF
addCMakeVariable CMAKE_BUILD_TYPE:STRING=Release

# >>> And in case you have some trouble with MESA related errors you can comment Hrvoje's additional
# lines, like this:
# HJ, 9/Aug/2011
#addCMakeVariable OPENGL_gl_LIBRARY:STRING=

# HJ, 9/Aug/2011
#addCMakeVariable VTK_USE_OPENGL_LIBRARY:BOOL=ON



At least this is the way I finally got OF-1.6-ext with ParaView3.10.1 running on a CentOS 5.3 (Kernel 2.6.18-128.4.1.el5) machine.

Hope that helps!

Cheers,

Pascal.


All times are GMT -4. The time now is 23:25.