CFD Online Logo CFD Online URL
www.cfd-online.com
[Sponsors]
Home > Forums > OpenFOAM Installation

paraview 3.10.1 compiling error (1.6-ext)

Register Blogs Members List Search Today's Posts Mark Forums Read

Reply
 
LinkBack Thread Tools Display Modes
Old   September 27, 2011, 10:19
Default paraview 3.10.1 compiling error (1.6-ext)
  #1
Senior Member
 
Vesselin Krastev
Join Date: Jan 2010
Location: University of Tor Vergata, Rome
Posts: 361
Rep Power: 10
vkrastev is on a distinguished road
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 is offline   Reply With Quote

Old   September 28, 2011, 07:15
Question
  #2
Senior Member
 
Vesselin Krastev
Join Date: Jan 2010
Location: University of Tor Vergata, Rome
Posts: 361
Rep Power: 10
vkrastev is on a distinguished road
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.
vkrastev is offline   Reply With Quote

Old   September 29, 2011, 05:07
Default
  #3
Senior Member
 
Elvis
Join Date: Mar 2009
Location: Sindelfingen, Germany
Posts: 577
Blog Entries: 5
Rep Power: 13
elvis is on a distinguished road
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
elvis is offline   Reply With Quote

Old   September 29, 2011, 05:45
Default
  #4
Senior Member
 
Vesselin Krastev
Join Date: Jan 2010
Location: University of Tor Vergata, Rome
Posts: 361
Rep Power: 10
vkrastev is on a distinguished road
Quote:
Originally Posted by elvis View Post
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.
vkrastev is offline   Reply With Quote

Old   September 30, 2011, 11:42
Default
  #5
Member
 
Jason Eason
Join Date: Jan 2010
Location: Portage, Michigan
Posts: 44
Rep Power: 7
JulytoNovember is on a distinguished road
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.
__________________
Debian Squeeze - OpenFOAM-2.1.x, Paraview-3.12.0
JulytoNovember is offline   Reply With Quote

Old   September 30, 2011, 11:48
Default
  #6
Senior Member
 
Vesselin Krastev
Join Date: Jan 2010
Location: University of Tor Vergata, Rome
Posts: 361
Rep Power: 10
vkrastev is on a distinguished road
Quote:
Originally Posted by JulytoNovember View Post
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 is offline   Reply With Quote

Old   October 10, 2011, 05:01
Default
  #7
Senior Member
 
Vesselin Krastev
Join Date: Jan 2010
Location: University of Tor Vergata, Rome
Posts: 361
Rep Power: 10
vkrastev is on a distinguished road
Quote:
Originally Posted by JulytoNovember View Post
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.
vkrastev is offline   Reply With Quote

Old   October 28, 2011, 03:17
Default fixed bundle problem solution
  #8
Member
 
P.A.
Join Date: Mar 2009
Location: Germany
Posts: 47
Rep Power: 8
blaise is on a distinguished road
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.
blaise is offline   Reply With Quote

Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


Similar Threads
Thread Thread Starter Forum Replies Last Post
error install Paraview 3.10.1 qt preibie OpenFOAM 6 August 24, 2011 16:11
Segmentation fault with paraview 3.10.1 aot OpenFOAM Paraview & paraFoam 2 July 25, 2011 13:43
OF-1.6-ext enable MPI in paraview compiling pcaron OpenFOAM Installation 2 March 7, 2011 18:58
paraview installation woes vex OpenFOAM Installation 15 January 30, 2011 08:11
paraFoam reader for OpenFOAM 1.6 smart OpenFOAM Installation 13 November 16, 2009 22:41


All times are GMT -4. The time now is 21:07.