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

Fonud a couple of script errors in 1.5-dev

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

Reply
 
LinkBack Thread Tools Display Modes
Old   July 6, 2009, 16:42
Default Fonud a couple of script errors in 1.5-dev
  #1
Senior Member
 
David Gaden
Join Date: Apr 2009
Location: Winnipeg, Canada
Posts: 397
Rep Power: 12
marupio is on a distinguished road
Reposting from a thread in OpenFOAM/Installation... the final post:

Found it.
There was a bug in the 1.5-dev buildParaView3.3-cvs script, as well as in the bashrc script under OpenFOAM-1.5-dev/etc/apps/paraview3. See below:

buildParaView3.3-cvs: (lines 42-50)
VERBOSE=OFF
INCLUDE_MPI=OFF
MPI_MAX_PROCS=32
#INCLUDE_PYTHON=OFF
INCLUDE_PYTHON=ON
PYTHON_LIBRARY="/usr/lib64/libpython2.5.so.1.0"
PYTHON_LIBRARY=""
INCLUDE_MESA=OFF

Comment out the second last line. Not sure why it's there.

OpenFOAM-1.5-dev/etc/apps/paraview3/bashrc: (line 45)
export ParaView_INST_DIR=$WM_THIRD_PARTY_DIR/ParaView-$ParaView_VERSION

Remove the `-`. i.e. change to:
export ParaView_INST_DIR=$WM_THIRD_PARTY_DIR/ParaView$ParaView_VERSION

I'll be repeating this under 'bugs'.
-dave
marupio is offline   Reply With Quote

Old   July 7, 2009, 05:05
Default
  #2
Assistant Moderator
 
Bernhard Gschaider
Join Date: Mar 2009
Posts: 3,915
Rep Power: 40
gschaider will become famous soon enoughgschaider will become famous soon enough
I just checked on 1.5.x and there are similar "issues" there. But I don't think that they are bugs per se, but that they reflect differences between installations (of paraview and python)

Quote:
Originally Posted by marupio View Post
Reposting from a thread in OpenFOAM/Installation... the final post:

Found it.
There was a bug in the 1.5-dev buildParaView3.3-cvs script, as well as in the bashrc script under OpenFOAM-1.5-dev/etc/apps/paraview3. See below:

buildParaView3.3-cvs: (lines 42-50)
VERBOSE=OFF
INCLUDE_MPI=OFF
MPI_MAX_PROCS=32
#INCLUDE_PYTHON=OFF
INCLUDE_PYTHON=ON
PYTHON_LIBRARY="/usr/lib64/libpython2.5.so.1.0"
PYTHON_LIBRARY=""
INCLUDE_MESA=OFF
You mean the second line with PYTHON_LIBRARY? Leave that and comment out the first one. Otherwise it will only work on 64-bit machines with a python 2.5 installation. Leaving the empty variant SHOULD make cmake search for the python-installation by itself.

Quote:
Originally Posted by marupio View Post
Comment out the second last line. Not sure why it's there.

OpenFOAM-1.5-dev/etc/apps/paraview3/bashrc: (line 45)
export ParaView_INST_DIR=$WM_THIRD_PARTY_DIR/ParaView-$ParaView_VERSION

Remove the `-`. i.e. change to:
export ParaView_INST_DIR=$WM_THIRD_PARTY_DIR/ParaView$ParaView_VERSION
This '-' depends on how the sources for Paraview were extracted (To a place with or without '-'

I'm afraid with the stuff in the etc-tree you've got to be aware that you'll have to do some fiddling if you pull them from one of the Source repositiories because there might be some things in there that are different from the binary release

Bernhard
gschaider is offline   Reply With Quote

Old   July 7, 2009, 18:45
Default
  #3
Senior Member
 
David Gaden
Join Date: Apr 2009
Location: Winnipeg, Canada
Posts: 397
Rep Power: 12
marupio is on a distinguished road
Quote:
Originally Posted by gschaider View Post
You mean the second line with PYTHON_LIBRARY? Leave that and comment out the first one. Otherwise it will only work on 64-bit machines with a python 2.5 installation. Leaving the empty variant SHOULD make cmake search for the python-installation by itself.
Fair enough. I guess cmake couldn't find it, or I've messed that up somehow too.

Quote:
Originally Posted by gschaider View Post
This '-' depends on how the sources for Paraview were extracted (To a place with or without '-'

I'm afraid with the stuff in the etc-tree you've got to be aware that you'll have to do some fiddling if you pull them from one of the Source repositiories because there might be some things in there that are different from the binary release

Bernhard
I think the '-' is a typo because it extracted without a '-', and the ParaView2.x bashrc script has it right...
marupio is offline   Reply With Quote

Old   July 8, 2009, 07:09
Default
  #4
Senior Member
 
Mark Olesen
Join Date: Mar 2009
Location: http://olesenm.github.io/
Posts: 777
Rep Power: 18
olesen will become famous soon enough
Quote:
Originally Posted by marupio View Post
I think the '-' is a typo because it extracted without a '-', and the ParaView2.x bashrc script has it right...
OTOH using a '-' delimiter is consistent with the naming convention used with various other ThirdParty packages (and rpm packages as well, incidentally).
It is also a convention that paraview uses internally too - ie, paraview searches a "lib/paraview-X.Y" path for its own components.
olesen is offline   Reply With Quote

Old   July 8, 2009, 09:32
Default
  #5
Senior Member
 
David Gaden
Join Date: Apr 2009
Location: Winnipeg, Canada
Posts: 397
Rep Power: 12
marupio is on a distinguished road
... a bit hypocritical of me, with a typo in the thread title... hehehe.
-dave
marupio is offline   Reply With Quote

Old   July 8, 2009, 13:17
Default
  #6
Assistant Moderator
 
Bernhard Gschaider
Join Date: Mar 2009
Posts: 3,915
Rep Power: 40
gschaider will become famous soon enoughgschaider will become famous soon enough
Quote:
Originally Posted by marupio View Post
Fair enough. I guess cmake couldn't find it, or I've messed that up somehow too.
In my experience cmake HAS a hard time finding the Python-installation. I guess that is one of the reasons why Python is not enabled in the buildParaview-script by default
gschaider 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
How to write k and epsilon before the abnormal end xiuying OpenFOAM Running, Solving & CFD 8 August 27, 2013 15:33
Convergence moving mesh lr103476 OpenFOAM Running, Solving & CFD 30 November 19, 2007 15:09
IcoFoam parallel woes msrinath80 OpenFOAM Running, Solving & CFD 9 July 22, 2007 02:58
Could anybody help me see this error and give help liugx212 OpenFOAM Running, Solving & CFD 3 January 4, 2006 19:07
Trimmed cell and embedded refinement mesh conversion issues michele OpenFOAM Other Meshers: ICEM, Star, Ansys, Pointwise, GridPro, Ansa, ... 2 July 15, 2005 04:15


All times are GMT -4. The time now is 20:18.